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
[EMAIL PROTECTED] 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
You mean that if
Hi Hugh,
Le 19 juin 07 à 16:59, [EMAIL PROTECTED] a écrit :
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
Just
I 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.
Martin Baxter wrote:
You
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
