Community
Participate
Working Groups
The initial size of the eclipse window when starting extends under the gnome panel at the bottom of the screen (and sometimes off the display) under linux when the display resolution is low (1024x768). This makes the status bar not visible. A new user might be confused if they do not alter the window position since loading progress is shown in the status bar. A user may believe that the application is frozen or not actually perfoming the action they requested. If the user's screen resolution is higher, the entire eclipse window starts onscreen and everything is visible. I suggest that the window be maximized initially if the display resolution is too small to show the screen readably. The issue here is that the display may be large enough to contain the window, but the gnome panel could be hiding a portion of it, so it is not simply a check to see if the window fits within the current screen resolution.
I'm going to forward this to SWT first to see if we can detect this situation.
The issue is described in bug 33659, and the problem is that there's no way to get the information we need from the window manager. However, _NET_WORKAREA from the freedesktop.org wm-spec is "close enough", so I have given up and checked in my fix. In 3.2M3 and up, on a non-Xinerama display, and under a compliant window manager (kwin and metacity work), Eclipse will always open fully visible. However, I think the initial window size of Eclipse is too large, and with the fix, the window now opens slightly-unmaximized which looks a little odd. A better strategy may be to open maximized at 1024x768 and lower. Note that many Linux machines default to 1024x768 with large panels. I'm moving this bug back to UI to please consider a smaller default size or a maximization strategy.
There are currently no plans to do this but we would be happy to look at a patch
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.
