Community
Participate
Working Groups
I20041216-1200, Solaris, Motif, CDE When all perspectives are closed now, a custom background colour and foreground colour are chosen. These colours are not configurably, and are non-standard (at least with respect to non-Windows apps). These should ideally play nice with either native widget toolkit theming (e.g., GTK+) or with Eclipse's homegrown theming.
The code is in IDEWorkbenchAdvisor.createEmptyWindowContents. It currently uses SWT.COLOR_DARK_GREY and SWT.COLOR_WHITE. If it's changed to use SWT.COLOR_TITLE_INACTIVE_BACKGROUND and SWT.COLOR_TITLE_INACTIVE_FOREGROUND, it looks acceptable on Windows, and should play well with the theme. Billy, do you have any suggestions for which values look good here on GTK? If possible, I'd like to stick to the predefined colours rather than defining new ones via the themes xpt.
The inactive title bar colours are not well defined on GTK+ (and seem to actually map to the inactive selection foreground and background colours). I am not sure what would be an appropriate choice here either. Using anything other than the default widget foreground and background makes the margins along the sides of the window stand out in a strange way. If it just drew a maximized editor area frame instead of using colours I think it might fix the blankness problem without getting into too much trouble with themes.
Deferring. We want to show extra instructions here, not just a blank editor area.
Doug, can we live with this as-is for 3.1?
I must confess that I'm finding the lack of interest expressed on a few bugs of this sort very disheartening. (Bug 62900, Bug 62903, and Bug 85581, for example). The cumulative effect of not paying attention to appearance on non-Windows platforms is an unprofessional overall appearance on non-Windows platforms. Now that I've had my chance to rant ... yeah, sure ... after 3.1 is fine.
Reassigning bugs in component areas that are changing ownership.
Is this still a problem in 3.3? PW
Changes requested on bug 193523
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.
