I think there was alreay a STR for that (with a possible solution):
http://www.fltk.org/str.php?L2823+P0+S-2+C0+I0+E0+QFl_Preference
Cheers,
chris
> Widget handle() method upon first use calls Fl::visible_focus() which through
> Fl::option() reads fltk standard preferences (that is (Fl_Preferen
On 03/20/13 14:26, Greg Ercolano wrote:
>Perhaps an easy hack is to modify this line in Fl_Decl_Type::open():
> message = c_check(c&&c[0]=='#' ? c+1 : c);
>..to instead read something like:
> if ( !strncmp(c,"namespace",9) &&
> !strcmp(c,"};") ) message = c_check(c&&c[0]=='#' ? c+1
On 03/20/13 13:51, Greg Ercolano wrote:
> Sorry I can't think of anything better; looks like fluid needs to
> be modified, because New->Code->Declaration complains about the unclosed
> brace.
I don't know fluid's code well at all, but it looks like the 'code check'
is due to the F
On 03/20/13 11:25, Gonzalo Garramuno wrote:
> I am trying to port my software from flkt2 to fltk1.3.
> However fluid1.3 complains due to lacking namespaces.
> Any chance of adding namespaces to fluid1.3 or a work-around?
To use a namespace, I'd think New->Code->Declaration, and set it to:
I am trying to port my software from flkt2 to fltk1.3. However fluid1.3
complains due to lacking namespaces. Any chance of adding namespaces to
fluid1.3 or a work-around?
___
fltk mailing list
fltk@easysw.com
http://lists.easysw.com/mailman/listinfo/
> > > Maximizing a window, then minimizing it to an icon in the taskbar,
> and
> > > then opening that same icon creates a window that covers up to the
> > > taskbar, but it is behind it. The problem shows in all demos of
> > > fltk2.0. Fltk1.2 seems fine.
> > > Can somebody help?
> >
> > Gonzal
>
> > Maximizing a window, then minimizing it to an icon in the taskbar, and
> > then opening that same icon creates a window that covers up to the
> > taskbar, but it is behind it. The problem shows in all demos of
> > fltk2.0. Fltk1.2 seems fine.
> > Can somebody help?
>
> Gonzalo,
>
> Do you *
Hi Ian,
microwindows is a piece coming from the past.
I have already realized several machines running with AMD Alchemy (MIPS), more
or less same horsepower as the actual one.
It was the usual work of putting together pieces (microwindows + nano-X,
truetype fonts and so on),
but it works.
Microwi
> Maximizing a window, then minimizing it to an icon in the taskbar, and
> then opening that same icon creates a window that covers up to the
> taskbar, but it is behind it. The problem shows in all demos of
> fltk2.0. Fltk1.2 seems fine.
> Can somebody help?
Gonzalo,
Do you *really* mean fltk
> just pure Linux & microwindows on a 400 MHz PowerPC embedded
> platform ;-)
If you have a 400 MHz PPC, is microwindows the best choice? That
should be easily able to run a "real" X11 server, (I'm thinking
of the TinxX / K-drive stuff, for example.)
I only ask because (admittedly a *long* time
> Maximizing a window, then minimizing it to an icon in the taskbar, and then
> opening that same icon creates a window that covers up to the taskbar, but it
> is behind it. The problem shows in all demos of fltk2.0. Fltk1.2 seems fine.
> Can somebody help?
This is in Windows. Linux works fin
Maximizing a window, then minimizing it to an icon in the taskbar, and then
opening that same icon creates a window that covers up to the taskbar, but it
is behind it. The problem shows in all demos of fltk2.0. Fltk1.2 seems fine.
Can somebody help?
_
Hi Albrecht,
> Also note that this timer delay compensation works well (i.e. as
> designed) on Linux, but probably not on Windows :-( I did some
> tests a while back, but lost track of it. I can't say anything
> about Mac OS WRT this.
No Windows here, m8 :
just pure Linux & microwindows on a 400
Widget handle() method upon first use calls Fl::visible_focus() which through
Fl::option() reads fltk standard preferences (that is (Fl_Preferences::SYSTEM,
"fltk.org", "fltk") and (Fl_Preferences::USER, "fltk.org", "fltk")).
Fl::option() function (Fl.cxx, line around 1944) just constructs these
On 19.03.2013 16:31, memoryl...@tin.it wrote:
> The problem was that, under particular conditions (many redraw of images), my
> blinking could become irregular,
> as timers, if I understand well, are all at the same "priority level".
Hint Fl::repeat_timeout() is designed to compensate for small
15 matches
Mail list logo