...indeed, hence the suggestion - to test whether the problem is non-text elements getting into the clipboard that LC doesn't like.
That way, you can at least prove whether you have the option to add LC-friendly pre-processing via a user-friendly Excel trick, such as a nice big 'Export to LC' button that drives a macro that will copy the range, paste-special-values somewhere and then copy clean text from there into the clipboard. On 13 Sep 2011, at 17:43, Colin Holgate wrote: > That would be more steps than what I do now, which is to just do a paste in > any other program, then the next paste into LiveCode works ok. > > > On Sep 13, 2011, at 12:36 PM, Keith Clarke wrote: > >> As you can control the source, is it worth (at least to test) saving the >> range into a CSV format to force everything to plain text. That way non-text >> elements shouldn't get into the clipboard? > > _______________________________________________ > 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