Bug 220922 - Standalone Spinner button
Summary: Standalone Spinner button
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Felipe Heidrich CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-29 07:15 EST by Martin Hoefer CLA
Modified: 2019-09-06 16:06 EDT (History)
2 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 Martin Hoefer CLA 2008-02-29 07:15:18 EST 
For different reasons, it may be useful to have a spinnerbutton as a separate swt widget. So the user can handle the up/down events for his own functionality.
Comment 1 Steve Northover CLA 2008-02-29 10:49:05 EST 
What?  Don't understand you at all ...
Comment 2 Kevin Barnes CLA 2008-02-29 11:32:57 EST 
Steve, he wants just the button, not the text field.
(ie something like new Button(parent, SWT.UPDOWN))
Comment 3 Steve Northover CLA 2008-02-29 11:45:22 EST 
Silly me.  He wants the win32 "buddy" thing.
Comment 4 Felipe Heidrich CLA 2008-02-29 12:10:14 EST 
Can't you use:
Button(parent, SWT.ARROW | SWT.UP);
Button(parent, SWT.ARROW | SWT.DOWN);
both in the same composite with a fill layout, it could be a custom widget.
Comment 5 Martin Hoefer CLA 2008-03-01 03:42:05 EST 
(In reply to comment #4)
> Can't you use:
> Button(parent, SWT.ARROW | SWT.UP);
> Button(parent, SWT.ARROW | SWT.DOWN);
> both in the same composite with a fill layout, it could be a custom widget.
> 

Of course we can use two buttons like that, but for consistent design, it is not usable.
Comment 6 Eclipse Webmaster CLA 2019-09-06 16:06:33 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.