DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Pending] Link: http://www.fltk.org/str.php?L2348 Version: 1.3-current I think that converting the text would be an acceptable solution if we can be sure that the application programmer has a feature to recognize the buffer/file modification and warn the user. AFAICT this is done in the proposal. I also saw that the popup window's text can be replaced - that's good. I have two suggestions: (1) Make it possible to disable the warning message entirely (but keep a flag so that the program can get the information). If done this way the programmer is free to do what s/he likes. This could probably be done by setting a callback function, with the default being the suggested warning popup message. (2) The proposed filter function can only convert single-byte character sets. Windows' "native" Unicode implementation UTF-16 can not be read and converted this way. Wouldn't it be better to have a filter with a char* (or char **) pointer and maybe a length return value or something like that so that we can also filter multi-byte encodings? Link: http://www.fltk.org/str.php?L2348 Version: 1.3-current _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
