I-beam Artifact bug?

[Peter T. Evensen]

Do you mean the flashing insertion bar gets stuck in the field when you 
set locktext to true?  This is already bug #4840  
http://quality.runrev.com/qacenter/show_bug.cgi?id=4840

You can work around it by adding a *type tab* before you set the 
locktext to true.  This defocusses the text filed (I couldn't figure out 
any other way that worked reliably), and removes the insertion point.

FlexibleLearning at aol.com wrote:
> Has anyone else noticed an I-beam artifact when locking a field?
>  
> Try this in a field on Win32...
>
> on mouseLeave
> set the  locktext of me to true
> end mouseLeave
>
> on mouseEnter
> set the  locktext of me to false
> end mouseEnter
>
> Not affected on OSX.
>
> /H
>  
>
>
>
>    
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>
>