[STR Closed w/Resolution]
Link: http://www.fltk.org/str.php?L2783
Version: 1.3-current
Fix Version: 1.3-current (r9366)
Fixed in Subversion repository.
Made sure internal cleanup still happens as suggested.
Updated documentation & mod adequately.
Link: http://www.fltk.org/str.php?L2783
Vers
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2783
Version: 1.3-current
No, you don't want to return.
Even if the string is NULL, the predelete/modify callbacks should still be
done, selections zeroed out.. basically
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2783
Version: 1.3-current
Would it not be best to simply return on encountering a null string;
there's no point doing needless processing, unless the desired effect on a
n
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
Link: http://www.fltk.org/str.php?L2783
Version: 1.3-current
Link: http://www.fltk.org/str.php?L2783
Version: 1.3-current
___
fltk-bugs mailing list
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?L2783
Version: 1.3-current
With the attached patch that checks if NULL is passed and set the parameter
to an empty string there is no segfault and I think the desired result
