I have never seen this behavior.
But I see that others have noticed the same irregularity. It is so fundamental, that I cannot imagine it is an engine issue, but rather must be some procedural thing, as Igor points out, though this seems odd to me. Peter, the "lockText" property would not allow a cursor in the field at all. Craig Newman -----Original Message----- From: Robert Brenstein <r...@robelko.com> To: How to use LiveCode <use-livecode@lists.runrev.com> Sent: Mon, May 21, 2012 9:09 am Subject: Re: insertion point glitch On 20.05.2012 at 21:28 Uhr -0700 Timothy Miller apparently wrote: >Hi, I do a fair amount of tedious data entry with my liveCode stacks. > >Now and then, a field's focus border is hilited, the cursor >insertion point is blinking in the field, but the field is >unresponsive to keyboard input. Clicking again in the field does not >make a difference. The only way to make the field responsive is to >click in another field, then click again on the field I want to type >into. > I keep seeing exactly that as well. I believe this is a glitch somewhere in the engine. I have seen it as far as version 2.6 and while working in MetaCard. It usually happens for me when selecting the field content with the mouse and accidently misclicking somewhere, I believe by the edge of the field. I never figured out the exact trigger, but since clicking elsewhere resets it, I learned to live with it and just watch to make clean clicks. Robert _______________________________________________ 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
