Bug 242719 - [JFace] SpinnerFieldEditor as a new type of FieldEditor
Summary: [JFace] SpinnerFieldEditor as a new type of FieldEditor
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-31 09:53 EDT by Mathias Schaeffner CLA
Modified: 2019-09-06 16:13 EDT (History)
2 users (show)

See Also:

Attachments
implementation of org.eclipse.jface.preference.SpinnerFieldEditor (11.00 KB, text/x-java)
2008-08-01 03:48 EDT, Mathias Schaeffner CLA 		no flags Details
View All 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 Mathias Schaeffner CLA 2008-07-31 09:53:00 EDT 
The package org.eclipse.jface.preference doesn't contain a FieldEditor of the type SpinnerFieldEditor, but the class ScaleFieldEditor.
There are cases when a spinner control is more appropriate instead of a scale control.
JFace should support this with a class SpinnerFieldEditor.
I implemented this as it is really trivial.
Just replace the scale control in ScaleFieldEditor by a spinner control.
Comment 1 Remy Suen CLA 2008-07-31 22:28:52 EDT 
(In reply to comment #0)
> JFace should support this with a class SpinnerFieldEditor.
> I implemented this as it is really trivial.
> Just replace the scale control in ScaleFieldEditor by a spinner control.

Would you be willing to contribute this code? :)
Comment 2 Mathias Schaeffner CLA 2008-08-01 03:48:29 EDT 
Created attachment 108933 [details]
implementation of org.eclipse.jface.preference.SpinnerFieldEditor
Comment 3 Susan McCourt CLA 2009-07-09 18:19:39 EDT 
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:13:19 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.