[STR Closed w/Resolution]
Link: http://www.fltk.org/str.php?L2687
Version: 1.3.1
Fix Version: 1.3-current (r9210)
Fixed in Subversion repository.
Link: http://www.fltk.org/str.php?L2687
Version: 1.3.1
Fix Version: 1.3-current (r9210)
___
fltk-bugs
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2687
Version: 1.3.1
OK - r9210 should do it...
Link: http://www.fltk.org/str.php?L2687
Version: 1.3.1
___
fltk-bugs mailing
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2687
Version: 1.3.1
OK - this is odd.
I never got any update emails form this STR, but I now see that Matt said,
on the 20th Sept., that we should try removing the code a
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2687
Version: 1.3.1
bump
Link: http://www.fltk.org/str.php?L2687
Version: 1.3.1
___
fltk-bugs mailing list
fltk-bugs@easysw.
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2687
Version: 1.3.1
Ian, would you please remove the code and close the STR? Thanks!
Link: http://www.fltk.org/str.php?L2687
Version: 1.3.1
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2687
Version: 1.3.1
+1 for remove it and see if this causes any trouble.
Link: http://www.fltk.org/str.php?L2687
Version: 1.3.1
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2687
Version: 1.3.1
I'd be inclined to remove the suspect code, perhaps?
Then see if anybody shouts...
It seems it may be working around some historical issue that has r
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2687
Version: 1.3.1
Any more ideas on this? Should we continue to wait for replies, or should
we leave or remove the code for 1.3.1 ?
Link: http://www.fltk.org/str.php?L
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2687
Version: 1.3.1
I've added a #warning message to the "suspect" code, in the hope that this
will let us see when/where/if it is ever actually used.
Though this will on
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2687
Version: 1.3.1
Adding to Greg's note above:
- This code is *not* used under the win32 targets, there is a separate
implementation in scander_win32.c for them; howeve
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2687
Version: 1.3.1
The issue being this appears to be GPL code
that is probably not compatible with our LGPL/static exception.
There's some question as to what platform(
11 matches
Mail list logo
