Summary: | MouseWheel events doesn't works. | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Arnaud <ademuyser> |
Component: | SWT | Assignee: | Felipe Heidrich <eclipse.felipe> |
Status: | REOPENED --- | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | steve_northover |
Version: | 3.2.2 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Arnaud
2007-10-23 05:18:22 EDT
I'm pretty sure this is not what the platform does. FH to confirm and then close this bug as WONTFIX (if he agrees). mouse wheel events do go up the hierarchy as you said. In your test case, the ScrollComposite named sc2 has a scrollbar bar (enabled, not visible). This scrollbar is first scrollbar in the hierarchy and it is the one consuming the events. The fix your app you need to subclass ScrolledComposite and override layout(Composite, boolean) to disable the scrollbars when they hostBounds is greater than contentBounds. ScrolledComposite's layout choose to set scrollbar visible or not depending on its content's size versus its client area. I don't understand why at this time ScrolledComposite won't fix the scrollbar enablement too. Why all ScrolledComposite users must subclass it to fix scrollbar enablement when this can be done once by swt.custom code ? Steve, does it make sense to send selection events to a not visible scrollbar ? We can change this in ScrollComposite or in Scrollable. (In reply to comment #4) > Steve, does it make sense to send selection events to a not visible scrollbar ? > We can change this in ScrollComposite or in Scrollable. Just to be clear, these selection events are generate by the mouse wheel. 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. |