t;
> You *can* indeed have more than one default button, but it's not a good idea.
> For the reasons you mentioned and more. On OSX having more than one default
> button will use up huge amounts of cpu power even while doing nothing more
> than
On 02/24/2017 03:13 PM, Bob Sneidar via use-livecode wrote:
Hi all.
I was given to understand that there can only be one default button. I see I am
mistaken. I thought that setting the defaultButton of a card unset the default
of the button that was the defaultButton prior to that. It seems
Hi all.
I was given to understand that there can only be one default button. I see I am
mistaken. I thought that setting the defaultButton of a card unset the default
of the button that was the defaultButton prior to that. It seems to me that
this is how this ought to work, because if not
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 on the engine to trap t
I have never relied on the engine to trap the default button activation
because it only works when nothing else is focussed.
Hugh Senior
FLCo
Perte wrote:
Thanks everyone.
Jacque, Like you I'm currently using a returnKey handler for the card that
sends mouseUp to the button to get round th
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
s machines. So pressing Enter
on Mac would give the expected behavior of completing the action. Look at the
LC script editor as an example of that.
On Sep 1, 2011, at 5:12 PM, Peter M. Brigham, MD wrote:
>
>
> That way, no matter where the focus is, the default button will get
on closecard -- or closestack, or whatever
remove the script of btn "myFrontscript" of this card from front
end closecard
That way, no matter where the focus is, the default button will get triggered
with a returnkey hit.
-- Peter
Peter M. Brigham
pmb...@gmail.com
http://home.comc
;
On Thu, Sep 1, 2011 at 10:59 AM, Bob Sneidar wrote:
> 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 defa
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 b
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
t irks me
> every time I have to do something with plugins. But I don't spend a lot of
> time configuring plugins.
>
> Give a choice between fixing these little things, I'd rather have them
> continue their building the a new full featured text field or built-in SFTP
>
button changing
size - is that in the defaultButton entry?
Mark, maybe the difference between what you did and what I have is that I
have 3 field controls on the card in addition to the default Button. Each
of the field controls has lockText set to true and traversalOn set to false.
Thing is, the
ive a choice between fixing these little things, I'd rather have them
continue their building the a new full featured text field or built-in SFTP
support.
Regarding the default button issue - quite frankly I'd rather have Livecode
give me the primitives and give me the ability to work with th
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
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
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
-Original Message-
From: Pete
To: How to use LiveCode
Sent: Wed, Aug 31, 2011 4:31 pm
Subject: Default Button
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
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 claimed by the dictionary. Is
25 matches
Mail list logo
