Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 369817 - Send scroll message to wrong component
Summary: Send scroll message to wrong component
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.2   Edit
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2012-01-26 10:43 EST by Lorenzo Rimondini CLA
Modified: 2020-03-03 18:49 EST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lorenzo Rimondini CLA 2012-01-26 10:43:32 EST 
Build Identifier: Version: 3.6.2 Build id: M20110210-1200

I have a ViewPart with a TreeViewer inside, when I try to scroll the Table inside an Editor, using mouse on scrollbar directly, the message is sent to the TreeViewer instead of to the TableViewer

Reproducible: Always

Steps to Reproduce:
1. Use TreeViewer in a ViewPart to open an editor with a TableViewer
2. Use mouse on TableViewer's scrollbar to scroll
3. TreeViewer scroll instead of TableViewer
Comment 1 Felipe Heidrich CLA 2012-01-30 11:36:34 EST 
Can attach a snippet, only using SWT if possible.

Note that in cocoa mouse wheel events are sent to the control under the mouse. On Windows, on the other hand, the events are sent to focus control.
Comment 2 Lakshmi P Shanmugam CLA 2012-08-06 07:26:24 EDT 
Do you see this with eclipse 3.8? I tried this in the dependencies tab in the plugin editor and couldn't see the problem. Can you reproduce it there? If not, can you provide a snippet showing the problem?
Comment 3 Eclipse Genie CLA 2020-03-03 18:49:57 EST 
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.