insertion point glitch

Robert Brenstein rjb at robelko.com
Mon May 21 12:04:00 EDT 2012


On 21.05.2012 at 10:14 Uhr -0400 dunbarx at aol.com apparently wrote:
>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.
>
>Craig Newman

I should have said: I keep seeing exactly that once a while as well.

As far as I can see, based on a few years of observation, it has to 
do with mis-clicking somehow. I don't know whether it is the position 
of the click or release or more conditions have to be met. However, 
whatever it is, it causes one part of the engine to think the field 
is not active for input while the other part of the engine shows that 
it is. I have a stack that I use for years for database input and 
once a while I get this behavior in one of the input fields, not 
always the same, whereas the stack works fine otherwise.

Robert




More information about the Use-livecode mailing list