To: How to use LiveCode
Sent: Sun, Jul 14, 2013 11:46 am
Subject: Re: excluding fields from tab-advancement
Then you could make the "non focusable" field "temporarily focusable" just to
allow data entry, it worked OK for my test…
==
on mouseDown
set the traversalOn of me t
Then you could make the "non focusable" field "temporarily focusable" just to
allow data entry, it worked OK for my test…
==
on mouseDown
set the traversalOn of me to true
focus on me
end mouseDown
on closeField
set the traversalOn of me to false
end closeField
on exitField
closeFi
On Sat, Jul 13, 2013 at 8:44 PM, wrote:
> The easiest way is to make the field non focusable. You can do this in the
> inspector or by script.
But then the user can't click in, can he?
Actually entering one of these to enter a value will be a rare event,
but I do want it to be possible.
--
Hi.
The easiest way is to make the field non focusable. You can do this in the
inspector or by script.
Craig Newman
-Original Message-
From: Dr. Hawkins
To: How to use LiveCode
Sent: Sat, Jul 13, 2013 8:35 pm
Subject: excluding fields from tab-advancement
I have some fields
I have some fields (e.g., totals that might need to be overridden for
reasons beyond my comprehension) that I want users to be able to click
into, but be excluded as the user tabs along in the "normal" fields.
I'm not seeing a clean way to do this.
I could intercept tabs, perhaps? Catch mouseUp
