And I might add, you may or may not get a trailing CR in a filter result depending on whether or not the whole chunk ended in a CR, regardless of whether or not the filter results CONTAIN the last line with the trailing CR.
I think the overriding principle now is that once a command or function which behaves a certain way is used in people's projects, RunRev is quite reticent to change it, because it *might* break people's code. That is the best argument I know of for leaving things the way they are. I believe that all languages have their odd little ways of doing things. Foxpro sure did! It's up to developers to work around things the way they are. JMHO Bob On Mar 20, 2012, at 10:17 AM, Pete wrote: > Lines don't have an insertion point, which seems to be the only reason that > a range with an end point less than a start point is valid in LC. They > have a terminating character (or separator depending on your point of > view); characters don't have a separator that delineates them from each > other. If you get the selectedLine, you will see either a single line > number if one line is selected or a line number range if multiple lines are > selected but you will never see a line range with the end line less than > the start line. _______________________________________________ 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
