Community
Participate
Working Groups
Hi, I try to change the background color of tabs when they're not active by putting the following extensions in my plugin.xml : <theme id="com.farbeyond.core.themes" name="Application Theme"> <colorOverride id="org.eclipse.ui.workbench.INACTIVE_TAB_BG_END value="COLOR_RED"/> </theme> (I know red is not appropriate color, but it's an example to show my point). The above extension works on tabs of views, i.e their background color turns into red when they're inactive, but it does not work on tabs of editors as their colors stays white, the editor tabs seem to ignore the extensions. Best Regards, Setya
Created attachment 19678 [details] Screenshot when the editor is active
Created attachment 19679 [details] Screenshot 2 when the view is active
Created attachment 19680 [details] Screenshot 3 expected tab color on inactive editor
(In reply to comment #0) > Hi, > I try to change the background color of tabs when they're not active by putting > the following extensions in my plugin.xml : > <theme id="com.farbeyond.core.themes" name="Application Theme"> > <colorOverride id="org.eclipse.ui.workbench.INACTIVE_TAB_BG_END > value="COLOR_RED"/> > </theme> > (I know red is not appropriate color, but it's an example to show my point). > The above extension works on tabs of views, i.e their background color turns > into red when they're inactive, but it does not work on tabs of editors as their > colors stays white, the editor tabs seem to ignore the extensions. > Best Regards, > Setya FYI, overriding org.eclipse.ui.workbench.INACTIVE_TAB_BG_START works for both view and editor tabs. Regards, Setya
We treat editors a bit special so that the active non-focus editor can be distinguished from other visible editors when there is more than one editor area. We should expose this colour via themes but we dont currently do it. I doubt we will have time to address this for 3.1.
(In reply to comment #5) > We treat editors a bit special so that the active non-focus editor can be distinguished from other visible > editors when there is more than one editor area. We should expose this colour via themes but we dont > currently do it. I doubt we will have time to address this for 3.1. (In reply to comment #5) > We treat editors a bit special so that the active non-focus editor can be distinguished from other visible > editors when there is more than one editor area. We should expose this colour via themes but we dont > currently do it. Actually we use editor parts for our data-centric form, not for editing file. That's why we don't want to have white as background, moreover we avoid using Eclipse Form API. Do you think editor is appropriate to be used for data-centric apps. >I doubt we will have time to address this for 3.1. So I have to wait for 3.2 ? Regards, Setya
(In reply to comment #6) > > Actually we use editor parts for our data-centric form, not for editing file. > That's why we don't want to have white as background, moreover we avoid using > Eclipse Form API. > > Do you think editor is appropriate to be used for data-centric apps. Yes, this is reasonable. > > >I doubt we will have time to address this for 3.1. > > So I have to wait for 3.2 ? Yes. Alternatively you could implement your own presentation. Presentations control how views and editors are displayed within the workbench. Stefan, are there any documents for presentations available? I should mention that doing this is NOT a trivial task... > > > Regards, > > Setya
(In reply to comment #7) > (In reply to comment #6) > > > > Actually we use editor parts for our data-centric form, not for editing file. > > That's why we don't want to have white as background, moreover we avoid using > > Eclipse Form API. > > > > Do you think editor is appropriate to be used for data-centric apps. > > Yes, this is reasonable. > > > > > >I doubt we will have time to address this for 3.1. > > > > So I have to wait for 3.2 ? > > Yes. Alternatively you could implement your own presentation. Presentations > control how views and editors are displayed within the workbench. Stefan, are > there any documents for presentations available? I should mention that doing > this is NOT a trivial task... > > > > > > > Regards, > > > > Setya > > When will this bug be resolved in 3.2 ? Regards, Setya
It's not so much a matter of when, but if. We haven't yet allocated any time for this problem. If you have a patch that can accomplish what you're asking for we would consider it.
This seems to still be a bug in Eclipse 3.3, any sort of timeline for a fix?
There is no timeline at this time but we will entertain patches.
Okay, I will take a look. I'm fairly new and can't promise anything. Currently thinking of trying to provide an additional set of colour preferences in order to colour the active non-focus editor different from a non-active non-focus visible editor, would this be a good idea?
Any changes to our color schemes will need to be run past Kevin.
Susan is now responsible for watching the [Themes] category.
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.
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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. -- The automated Eclipse Genie.
