Bug 78976 - [consistency] Scale Selection event never has detail
Summary: [consistency] Scale Selection event never has detail
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.1   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Grant Gayed CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-18 12:31 EST by Grant Gayed CLA
Modified: 2019-09-06 16:06 EDT (History)
1 user (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 Grant Gayed CLA 2004-11-18 12:31:32 EST 
- run the ControlExample, go to its Slider/Scale tab
- listen for Selection events
- give focus to the example Scale widget
- change its value with Left/Right-Arrow, PageUp/Down, Home/End, mouse clicks 
and drags, etc., and note that the fired Selection event detail fields are 
always 0
- doing the same with the example Slider widget above the Scale widget always 
fills in the detail field correctly; Scale should do this too
Comment 1 Steve Northover CLA 2004-11-19 17:07:30 EST 
Not sure if it's possible to get this information from the underlying widget 
for Scale on all platforms.  If even one platform can't provide it, we should 
close this PR as WONTFIX.
Comment 2 Steve Northover CLA 2004-11-19 17:08:15 EST 
Marking as consistency because Scale seems inconsistent with Slider and the 
rest of the SWT API.
Comment 3 Grant Gayed CLA 2004-11-30 09:08:23 EST 
note bug 51995 for gtk
Comment 4 Steve Northover CLA 2005-01-19 19:48:24 EST 
Grant to prioritize.
Comment 5 Eclipse Webmaster CLA 2019-09-06 16:06:29 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.