Bug 300367 - [Coolbar] Visual hover defect for toolbar buttons added by menu contributions.
Summary: [Coolbar] Visual hover defect for toolbar buttons added by menu contributions.
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5.1   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-21 08:56 EST by Kai Schlamp CLA
Modified: 2019-09-06 15:31 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kai Schlamp CLA 2010-01-21 08:56:42 EST
Build Identifier: 20090920-1017

1. Contribute a button (or better to say a command) by using the menu contributions to a view toolbar.
2. Add handler programmatically for that command that disables itself (using the setBaseEnabled method when activated).
3. Add another button somewhere (maybe inside the view), that programmatically enables the above handler again (also by using the setBaseEnabled method of the above handler).
3. Move with the mouse pointer over the button in the toolbar. The button correctly gets that normal hover decoration.
4. If the button is clicked then it gets disabled.
5. When the mouse pointer leaves the disabled toolbar button and click the other button (the one of step 3) then the toolbar button is enabled again, but still has the hover decoration (although the mouse pointer isn't above that toolbar button anymore).

-> wrong hover decoration of toolbar button.

Reproducible: Always
Comment 1 Eric Moffatt CLA 2010-01-21 13:47:21 EST
Kai, any chance you could rig up a test example for this ? Anything that repro's the issue will make it much easier for me to tackle...
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:31:09 EDT
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.