I think the key is 'focused object',
which can change based on user interaction and code execution.
A front script could test for the focused object, after trapping the
correct key stroke, then taking the desired action.
This could also be modified by a user preference or check box, as some
'Default' determines the button's visual appearance, and on some platforms
the change in border will grow the button dimensions a bit.
It's behavior should be up to the designer, by Enter and/or Return key
stroke, EnterInField and/or ReturnInField key stroke, or indeed none.
I have never relied o
over again, and no beeps of
any kind at all, no matter what I do, unless, of course, I click the
actual button itself.
>
> OXS 10.4.11 LC 4.5.3
>
> Craig
>
>
-Original Message-
> From: Mark Schonewille
> To: How to use
LiveCode
> Sent: Thu, Sep 1, 2011 8:29 am
yes
On 1 September 2011 14:47, Colin Holgate wrote:
> Good to know. As a point of interest, can you still trap for the Enterkey,
> while editing a field?
>
> On Sep 1, 2011, at 5:43 PM, Richard Gaskin wrote:
>
> > Peter's script traps returnKey, which is not sent when the Return key is
> hit whi
Colin Holgate wrote:
As a point of interest, can you still trap for the Enterkey, while editing a
field?
If the focus is on an open field, the enterInField message is sent instead.
--
Richard Gaskin
Fourth World
LiveCode training and consulting: http://www.fourthworld.com
Webzine for Live
Good to know. As a point of interest, can you still trap for the Enterkey,
while editing a field?
On Sep 1, 2011, at 5:43 PM, Richard Gaskin wrote:
> Peter's script traps returnKey, which is not sent when the Return key is hit
> while an open field has focus; in that circumstance the returnInFi
Colin Holgate wrote:
Need this be a good thing? If you're typing into a multiline field you might
not be finished at the time you press the Return key. On Mac at least there's
the convention that the Enter key might complete the action, and the Return key
is just a line break. Not sure how it
Need this be a good thing? If you're typing into a multiline field you might
not be finished at the time you press the Return key. On Mac at least there's
the convention that the Enter key might complete the action, and the Return key
is just a line break. Not sure how it is on Windows machines.
My solution has been to put the following in an invisible button:
on returnkey
send "mouseup" to btn "myDefaultBtn"
end returnkey
and then
on opencard -- or openstack, or whatever
insert the script of btn "myFrontscript" of this card into front
end opencard
on closecard -- or closestack,
I have entered this as a bug - it's #9707.
Bob, I can't reproduce what you did with the mouseUp at the card level.
Doesn't trigger for me under the circumstances you described. It DOES
trigger when I CLICK on the card outside of any controls on it as you'd
expect, but not when I hit return subse
t all, no matter
> what I do, unless, of course, I click the actual button itself.
>
>
> OXS 10.4.11 LC 4.5.3
>
>
> Craig
>
>
>
>
>
> -Original Message-
> From: Mark Schonewille
> To: How to use LiveCode
> Sent: Thu, Sep 1, 2011 8:29 a
I'm going to say that an active control is one that is not disabled and is
targeted. I created a new stack, with only one card and one button. In the
mouseUp of the button I put:
answer "This is the default button" as sheet
Hitting the return key triggers the mouseUp in the button. All well and
ual button itself.
OXS 10.4.11 LC 4.5.3
Craig
-Original Message-
From: Mark Schonewille
To: How to use LiveCode
Sent: Thu, Sep 1, 2011 8:29 am
Subject: Re: Default Button
Hi,
This is what I just did:
1) create new stack
2) drag one default button from the tools palette into yo
for the dictionary's comments about the defaultButton "changing its
> size",
> > etc. I never saw any of that.
> >
> >
> > This was all tried in a new mainStack with two rectangle buttons and a
> > single default button.
> >
> >
> > Craig
Thanks everyone.
Jacque, Like you I'm currently using a returnKey handler for the card that
sends mouseUp to the button to get round this.
Craig, If I "put the defaultbutton of this card", I get the correct output.
Also, I'm not seeing anything in the dictionary about the button changing
size -
iginal Message-
> From: J. Landman Gay
> To: How to use LiveCode
> Sent: Thu, Sep 1, 2011 7:22 am
> Subject: Re: Default Button
>
>
> On 8/31/11 7:29 PM, Pete wrote:
> > I put a default button a card that has a couple of field controls on it.
> > The fiel
Hi,
This is what I just did:
1) create new stack
2) drag one default button from the tools palette into your stack
3) edit the script of the button to make it been on mouseUp (and nothing else)
4) compile and close script
5) press return
6) hear beep
--
Best regards,
Mark Schonewille
Economy-x
e defaultButton "changing its size", etc. I never saw any of
that.
This was all tried in a new mainStack with two rectangle buttons and a single
default button.
Craig
-Original Message-
From: J. Landman Gay
To: How to use LiveCode
Sent: Thu, Sep 1, 2011 7:22 am
Subject: Re: De
On 8/31/11 7:29 PM, Pete wrote:
I put a default button a card that has a couple of field controls on it.
The field controls all have lockText set to true and traversalOn set to
false. Pressing the return key when the card is active does not execute the
mouseUp handler for the default button as
On 31.08.2011 at 17:29 Uhr -0700 Pete apparently wrote:
I put a default button a card that has a couple of field controls on it.
The field controls all have lockText set to true and traversalOn set to
false. Pressing the return key when the card is active does not execute the
mouseUp handler fo
I can only get this to work intermittently. The stuff in the dictionary does
not happen, and I cannot get a mouseUp message to fire.
If I set the default of a certain button I cannot get anything to return that
fact. (answer the defaultbutton of this cd)
But sometimes it does.
Craig Newman
21 matches
Mail list logo
