Hi,
I believe that 1.3 it's pretty stable ... but why then hasn't it been 
officially released as stable?
Moreover, I think I saw a bug report mentioning API changes between 1.1.x and 
1.3, but those changes aren't documented .. is it?

I was already considering fixing something in 1.1.9, but indeed then I'm on my 
own and its' pretty convenient to lift with the framework's improvements ...
To the other side, I'm a fltk novice and it's pretty time -consuming to dig in 
to such a level that lets me modify the framework without making a mess of it.

another thought: it seems to me nobody wants to fix anything in 1.1.9, why is 
that? as long as there isn't any other stable release, I'd think i'ts worth to 
merge bugfixes, at least the lightweight, like this draw()-related one.

> That's one of the beauties of open-source software -- if it doesn't do
> exactly what you need it to do, you can always tweak it a bit.
>
> Since the 1.1.x series is by definition "stable", you could back-port
> those kinds of change(s) into your own copy, without too much concern
> that a new, required release will break your local changes.
>
> Of course, you're probably then on your own when you need to ask others
> for help...
>
> That said, 1.3 has been perfectly stable for me.  Every time I've
> encountered a problem, it's turned out to be my code, not the toolkit's.
>
> -scott.
>
>
> On Wed, 2009-02-11 at 06:49 -0800, Fabio Bracci wrote:
> > >
> > >
> > > > > P.S. I filed STR # 2142, see http://www.fltk.org/str.php?L2142
> > > >=20
> > > > thanx! I'm working with fltk 1.1.9, I need a stable platform,=20
> > > > do you believe such bugfixes will be ported down to it?
> > >
> > > Unlikely to be back-ported in to the 1.1.x series - ABI
> compatibility.
> >
> > Hmmm ... then when will 1.3 reach a stable release?

_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to