On 8/11/13 9:55 PM, Mike Kerner wrote:
Also remember that text editors don't behave this way, either. Empty <CR>'s at the end of a line still trigger a page break. That seems far more correct than having to figure out of a delimiter/terminator should be significant or not.
Empty crs in LiveCode are also separate lines if there is no non-delimiter text preceding them.
But what you're describing is a visual effect implemented by word processors (and LiveCode fields.) They place the insertion point after the character you just typed. If you just typed a cr, then the insertion point is placed after it -- and since a cr marks a line ending, the insertion point shows up where the next "line" would start -- even though there really isn't one yet.
If you show invisible characters in a word processor, the cr is always placed at the end of the paragraph text, and is considered part of that paragraph. If you click after the cr terminator, the displacement of the cursor is visual only, indicating where your next character will display.
I do sympathize with your database dilemma though, I'm just not sure how to solve it -- and I'm not good enough with databases to even make a guess. But I don't think it would be wise to alter a behavior that's been in place for 26 years. Maybe some creative thinking by folks who know more about it will happen.
-- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com _______________________________________________ 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
