Community
Participate
Working Groups
Build Identifier: 3.6 GA On its own, the status bar for a text editor displays 3 things, the Editable/Read-only status, the Insert/Overwrite Status, and the Line/Column number. Other plugins may contribute additional widgets to the status bar of eclipse (sorry if terminology is wrong). When you change the size of the IDE, if it becomes too small to display all the contributions, then the the status bar height increases to hold multiple rows of contributions so they can all be seen. The problem i am reporting is that while the layout after window resize seems to make sure all the contributions get displayed by moving them around, the Text Editor status bar can get truncated. Typically, there is no re-layout if the Line Number / Column text is not visible for me. Also, when extending the text editor, and contributing my own StatusLineContributionItem to the end of the Text Editor status bar, using: TextEditorActionContributor.contributeToStatusLine() if i add my own contribution using: statusLineManager.add(myStatusLineContributionItem); My contributions to the text editor status line will also be truncated along with the line/column number display when the status bar is crowded with contributions Reproducible: Always Steps to Reproduce: 1.Open a file in the eclipse text editor 2.Change the IDE size until the column/line indicator is not visible. 3.(really needs multiple contributions to status line for real world scenario of how easy it is in 1024*768 I'm using default eclipse settings, windows XP, Large Size (120 DPI) if its relevant.
> then the the status >bar height increases to hold multiple rows of contributions so they can all be >seen. The status line does not have multiple rows. What you see being put on the next line is e.g. the Progress bar contribution. This is a general issue in org.eclipse.jface.action.StatusLine.
Created attachment 182834 [details] PerspectiveBar
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
