Hmm, now, I seem to recall that Jason Bryan's FLU widget extensions
=
for fltk had something like that - they wo uld be worth a look.
OK; his pages at OSC.edu appear to be down, but there's a mirror here
=
that still seems to work:
This came up a year ago - check STR2795
Latest
Thank you all so much for your hints: now I understand the real purpose
and design of Fl_tile!
I think I'll opt for a derived Fl_Group as suggested by Ian and Greg.
Mainly by Greg, I thought his description was pretty good.
I might be tempted to make his resizer widget out of a group, so that
... Jason Bryan's FLU widget extensions
... OK; his pages at OSC.edu appear to be down,
This came up a year ago - check STR2795
Latest FLU is hosted on sourceforge
http://sourceforge.net/projects/flufltk/
... does that actually work for anyone? I just tried, and there
don't seem to be
On 04/21/13 10:50, Greg Ercolano wrote:
I made one of these once; in my case I didn't use a tile,
just used a regular Fl_Group in which the widgets were positioned,
and put a thin widget between each that acted as a 'resizer' which:
1) enlarged/shrunk the
On 18.04.2013 15:09, Duncan Gibson wrote:
In Fl_Slider.H there are definitions that are used for subclasses:
pre
// values for type(), lowest bit indicate horizontal:
#define FL_VERT_SLIDER 0
#define FL_HOR_SLIDER 1
#define FL_VERT_FILL_SLIDER 2
On 18.04.2013 18:52, Greg Ercolano wrote:
I usually try to avoid type(), because while looking at
FLTK's own code, I've seen coding techniques that disagree
with the above, namely:
Fl.cxx:if (w-type()=FL_WINDOW) {dx -= w-x(); dy -= w-y();}
Fl.cxx: if (p-type() =
On 18.04.2013 23:44, Duncan Gibson wrote:
I saw the other comment in the docs about type() that it was a
hold over from the Forms implementation.
Please ignore Forms compatibility. We're going to remove this, and
AFAICT Matt has removed everything Forms related in FLTK 3.0.
I was struggling
7 matches
Mail list logo
