I agree. I am not much for the idea that software should change anything in the clipboard, as they cannot possibly predict why I am pasting it or what the clipboard "should" contain. We have all heard about the problems people have had with Microsofts own clipboard translation technology. It's obviously necessary, otherwise how would a text app know how to paste spreadsheet data?
But for the receiving app itself to presume to alter the contents of the clipboard, well that can get ugly. The closest I can envision as acceptable is a warning upon paste that the clipboard contains non-compatible characters. Otherwise, having the compiler ignore them seems the better solution. Bob On Sep 19, 2011, at 10:54 AM, Colin Holgate wrote: > Even if pasting could be fixed to remove carriage returns, or change them to > carriage return and line feed (whatever it is that is required), that > wouldn't fix existing scripts. What you said about the compiler processing it > based on how it looks would take care of the issue. > > > On Sep 19, 2011, at 1:43 PM, Dar Scott wrote: > >>> I think the number of people who manage to introduce an extra carriage >>> return character is going to be low, so not such a big deal. >> >> I wonder if this can be considered a paste issue. > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
