DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2849 Version: 1.3-current +1 to hide platform differences as well, but wondering if we shouldn't provide an option to turn this off if for some reason the app wants the original data. For instance, say a user is pasting the following string from one editor to another: "file:///some/path.txt, and today the humidity was %20." ..would the patch convert the %20 to a space? Or if they pasted an escaped URI, would they be surprised to find the URI unescaped after the paste operation? Also: would suggest adding error checking to the sscanf(); patch; if the sscanf() != 1, might be a good reason to abort the unescape operation entirely. If a URI is 'escaped' (or hex encoded), then it probably makes sense to stop parsing as soon as you hit a character that would normally be escaped (like a space), to avoid unescaping beyond the URI itself. Link: http://www.fltk.org/str.php?L2849 Version: 1.3-current _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
