DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.

[STR New]

Link: http://www.fltk.org/str.php?L2951
Version: 1.4-feature


Can't say regarding [1] or [2].

For [3], I'd say google for "double slider widget" and "range slider"
and see what you can gather in the way of options. And maybe check out
those widget's API to see if they have anything clever.

I guess such things can be used for everything from temperature to
date ranges. For the latter, it sounds like a app-provided callback
could be used to convert numeric values to/from strings such as dates.

Options I noticed from doing the above google searches:

    > a graticule option
    > drawing an optional box between the tabs
    > ability to drag the above box (to move both tabs locked together)
    > option to show text fields above and below the tabs
    > options for text fields to be editable
    > options for text fields to include up/down arrows
    > options for text fields to be integer vs. float
    > support Fl::scheme("gtk+") (and possibly "plastic")
    > arrow shaped "tabs" instead of raised rectangles (tinypic link
below)
    > option to show high/low values above or to side of slider
      at all times (instead of as a tooltip),eg:
     
http://content.w3avenue.com/2009/components/jquery-ui-slider-from-select-element/cover.jpg
    > data string callback (or virtual method) that lets the app
      convert numeric values to app defined strings (such as
      int<->date conversion)

Also: this little 'gif video' is neat; a bit over the top with
features, but it shows the 'dragging tab lock' mentioned above:
http://www.slicer.org/slicerWiki/images/6/6b/VolumesModuleWindowLevelSliderPopup.gif
Also:
http://dribbble.s3.amazonaws.com/users/58823/screenshots/303390/slider.png
http://i48.tinypic.com/2ebsn5i.jpg

Regarding [4], yes, I think a min/max for the entire range would be
needed, unless you wanted it to be a fixed 0.0 to 1.0 range slider,
which might simplify the API, but makes the user's job harder.
(Seems the widget should try to support values the app would want,
including ints, floats, and perhaps even strings as described above)

Of course doing all the above is probably too much, but perhaps it'll
give some idea as to how to design the widget so that such features
could be provided by the app by its overloading the widget.


Link: http://www.fltk.org/str.php?L2951
Version: 1.4-feature

_______________________________________________
fltk-dev mailing list
fltk-dev@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to