On 15.11.2010, at 22:45, Martin Kroeker wrote:
>> In the mean time, I will try to find all the .10 -> .11 conversions.
>
> Can we also get the fix for STR #2384 backported to 1.1.11 please ?
Why don't you move up to 1.3?
___
fltk-dev mailing list
flt
> In the mean time, I will try to find all the .10 -> .11 conversions.
Can we also get the fix for STR #2384 backported to 1.1.11 please ?
Martin
___
fltk-dev mailing list
fltk-dev@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk-dev
On 15.11.2010, at 21:23, Greg Ercolano wrote:
> Matthias Melcher wrote:
>> On 15.11.2010, at 19:06, Albrecht Schlosser wrote:
>>
>>> Maybe we should also update (some of) the image libs, because
>>> there are some security updates, but we need to check this.
>>> I'm not keen on finding out that
Matthias Melcher wrote:
> On 15.11.2010, at 19:06, Albrecht Schlosser wrote:
>
>> Maybe we should also update (some of) the image libs, because
>> there are some security updates, but we need to check this.
>> I'm not keen on finding out that we need to update FLTK's image
>> libs because of incom
Matthias Melcher wrote:
> On 15.11.2010, at 19:06, Albrecht Schlosser wrote:
>
>> Maybe we should also update (some of) the image libs, because
>> there are some security updates, but we need to check this.
>> I'm not keen on finding out that we need to update FLTK's image
>> libs because of incom
On 15.11.2010, at 19:06, Albrecht Schlosser wrote:
> Maybe we should also update (some of) the image libs, because
> there are some security updates, but we need to check this.
> I'm not keen on finding out that we need to update FLTK's image
> libs because of incompatibilities.
No, please. This
Duncan Gibson wrote:
> That just leaves 2302, which I think is the wrong STR number cos the
> Roadmap line and the STR text don't match. But maybe it's a biggie!
Yep, 2302 is definitely the wrong STR number (must be 2303).
Just fixed on the web site.
> PS Maybe making the STR # on the Roadm
Matthias Melcher wrote:
> there are three bugs in FLTK 1.1.10 that can cause a crash in some
> configurations. All of these have a working and somewhat verified patch.
I've also thought of doing another update for a while.
Maybe we should also update (some of) the image libs, because
there are
> there are three bugs in FLTK 1.1.10 that can cause a crash in some =
> configurations. All of these have a working and somewhat verified patch.
>
> Please vote +1, if we should take the time to release 1.1.11, or -1 if =
> we should focus on 1.3.0 only.
0 from me :-)
Of the 6 outstanding STRs
Matthias Melcher wrote:
> Hi guys,
>
> there are three bugs in FLTK 1.1.10 that can cause a crash in some
> configurations. All of these have a working and somewhat verified patch.
>
> Please vote +1, if we should take the time to release 1.1.11, or -1 if we
> should focus on 1.3.0 only. I assu
On Mon, 15 Nov 2010 13:56:50 +0100
Matthias Melcher wrote:
> there are three bugs in FLTK 1.1.10 that can cause a crash in some
> configurations. All of these have a working and somewhat verified patch.
>
> Please vote +1, if we should take the time to release 1.1.11, or -1 if we
> should focu
Hi guys,
there are three bugs in FLTK 1.1.10 that can cause a crash in some
configurations. All of these have a working and somewhat verified patch.
Please vote +1, if we should take the time to release 1.1.11, or -1 if we
should focus on 1.3.0 only. I assume it will take me the same time it w
12 matches
Mail list logo
