Mark,
This isn't true. If the traversalOn of a button it true, it can have focus.
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xtalkprogrammer
KvK: 50277553
Installer Maker for LiveCode:
Mark Schonewille m.schonewille@... writes:
This isn't true. If the traversalOn of a button it true, it can have focus.
Right. I stand corrected.
But that doesn't apply to menu buttons.
--
Mark Wieder
ahsoftw...@gmail.com
___
use-livecode
Mark,
Wrong again. Create a menu button, set its traversalOn to true, press
tab and use the arrow keys to navigate the menu.
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xtalkprogrammer
Mark Schonewille m.schonewille@... writes:
Wrong again. Create a menu button, set its traversalOn to true, press
tab and use the arrow keys to navigate the menu.
Hmm... I did that before posting. I'm unable to have the focusedObject be a
menu button on osx. I'll check again when I get the
On 10/10/2014, 4:55 PM, Mark Wieder wrote:
Mark Schonewille m.schonewille@... writes:
Wrong again. Create a menu button, set its traversalOn to true, press
tab and use the arrow keys to navigate the menu.
Hmm... I did that before posting. I'm unable to have the focusedObject be a
menu button
Not sure why it matters. You cannot tab to an OS X button even if traversal on
is true, unless of course you set some system property that escapes me at the
moment to make you stack look and act like an ugly OS 9 hypercard-ish
monstrosity. I even tried scripting to focus on the button, but it
Mark,
It might be different on OSX. I'm using Windows today. Also, I've now
noticed that you need to click in the card and not on the title bar to
enable navigation by arrow keys --seems a small bug to me.
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engineering
Mark Schonewille m.schonewille@... writes:
It might be different on OSX.
It's *very* different on osx, or at least different from linux, because on
osx the menubar takes on a life of its own and is no longer visually on the
card.
--
Mark Wieder
ahsoftw...@gmail.com
That's true, Mark, but my point was only that menu buttons can have
focus. Apparently, it doesn't make a difference to OP.
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xtalkprogrammer
KvK:
The OP wondered why the focusedObject didn't work for buttons on OS X. It's
because buttons can't have focus there.
On October 10, 2014 6:13:29 PM CDT, Mark Schonewille
m.schonewi...@economy-x-talk.com wrote:
That's true, Mark, but my point was only that menu buttons can have
focus.
Mark Schonewille m.schonewille@... writes:
That's true, Mark, but my point was only that menu buttons can have
focus. Apparently, it doesn't make a difference to OP.
No, that's *exactly* the point. If you look at the code in his sample stack,
he's tracking the focusedObject when a menu
Mark,
Thanks for the clarification but if you have the patients to explain a bit
further it would be appreciated. When the sub stack field has the focus, the
“long name of the focused object” refers to a card of the main stack (at least
there is no reference to a sub stack). For the first
John-
My apologies - I forgot about the weirdness of menus on osx.
My earlier response was based on linux, which has a much more reasonable
approach to UI interaction.
So here's what I see happening on osx:
1. click in the substack field
2. click on a menu item
This actually moves the focus to
I’m curious if the button itself is focusable. Instead, call a function in the
card script and use send in time. If it still results in two different objects,
then Houston, we have a problem.
Bob S
On Oct 8, 2014, at 22:02 , John j...@onechip.com wrote:
I have found a circumstance where
I did not try this from a menu, but it works as advertised from an ordinary
button.
Craig
On Oct 8, 2014, at 22:02 , John j...@onechip.com wrote:
I have found a circumstance where the long name of the focusedObject” and
“the focusedObject” refer to different objects in the same line of
On 10/9/2014, 1:15 PM, Bob Sneidar wrote:
I’m curious if the button itself is focusable.
Buttons are focusable on Windows and Linux but not on OS X.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
Mark,
I can see your line of reasoning but it does not quite track. The first
line in the result field does show that the focus is with main stack card where
the menu buttons are located. In my case, the second line indicates that the
focus is on the sub stack field, *not* the result
Jaque,
While this may be the case in general, when the menubar script is:
on mouseDown
put the long name of the focusedObject return return the
focusedObject into field results
end mouseDown
The first part of the put (the long name of the focusedObject) results in a
card on the
On 10/9/2014, 2:10 PM, John wrote:
While this may be the case in general, when the menubar script is:
on mouseDown
put the long name of the focusedObject return return the focusedObject into
field results
end mouseDown
The first part of the put (the long name of the focusedObject)
The fog is lifting a bit and I can see why the card gets the focus. That
the focusedObject can change part way through a single line of script is a bit
unsettling. The original goal was to access a property of a field to update
the menus before they are shown and using the selectedField
Certainly true about buttons not being focusable on OSX, not so sure about
the focus changing when the button is clicked.
I put the cursor into a field on a card then entered this in the message
box:
put the long name of the focusedObject return the focusedObject
The first line of the output
On 10/9/2014, 3:22 PM, John wrote:
The fog is lifting a bit and I can see why the card gets the focus.
That the focusedObject can change part way through a single line of
script is a bit unsettling. The original goal was to access a
property of a field to update the menus before they are shown
John john@... writes:
If I am thinking about this right, it means that the focusedObject was
changing during the execution of the single line script.
Yes, that's what I was trying to say. Sorry if it wasn't clear.
--
Mark Wieder
ahsoftw...@gmail.com
Mark,
Rereading what you wrote it is clear - I was just being a bit thick. Some
days it seems to take a while to get through.
Thanks,
John
On Oct 9, 2014, at 5:09 PM, Mark Wieder mwie...@ahsoftware.net wrote:
John john@... writes:
If I am thinking about this right, it means that the
John-
Thursday, October 9, 2014, 5:37:34 PM, you wrote:
Rereading what you wrote it is clear - I was just being a bit
thick. Some days it seems to take a while to get through.
Well, to be fair, understanding what's going on here is not at all
straightforward.
--
-Mark Wieder
I just tried the same thing using versions 6.6.2 and 5.0.2 with the same
result so I am guessing that I am missing something given this is how it has
worked for a long time. Apparently the combination of “name” with the
“focusedObject” doesn’t do what I would intuitively think. It still
Hi.
I could not open your stack. It was reported as corrupted. MacBook Air. OS
10.6.8 LC 6.3
Craig Newman
-Original Message-
From: John j...@onechip.com
To: How to use LiveCode use-livecode@lists.runrev.com
Sent: Thu, Oct 9, 2014 1:02 am
Subject: Is this a bug or am I missing
Craig,
Sorry about that. It was saved the latest (7.0 RC2) format. The following:
https://www.dropbox.com/s/yxmf3ysrski1osz/Test%20stack%20%282.7%29.livecode?dl=0
is saved in an older format that should open in LC 6.3. Unfortunately the
“.txt” still need to be removed.
Thanks,
John
On
Craig-
Wednesday, October 8, 2014, 10:23:14 PM, you wrote:
I could not open your stack. It was reported as corrupted. MacBook Air. OS
10.6.8 LC 6.3
It's in LC 7 format.
--
-Mark Wieder
ahsoftw...@gmail.com
This communication may be unlawfully collected and stored by the National
John-
Buttons can't receive focus. The focus of your mainstack is on the
only control that can receive a focus, the result field.
And it doesn't matter that you have clicked in the substack first. The
act of clicking in the menu shifts the focus to the main stack.
What you are seeing in the
30 matches
Mail list logo
