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 main stack being written to the “results” field and the second part
of the put (the focusedObject) results in the field on the sub stack being
written to the “results” field. If I change the script to:
on mouseDown
local theObject
put the focusedObject into theObject
put the long name of theObject & return & return & theObject into field
"results"
end mouseDown
The execution changes and the “result” field displays the same object (the
field on the subs tack) for both halves of the put being written to the
“results” field albeit in a different format.
This is leading me to the conclusion, perhaps incorrectly, that the
focusedObject is changing during the execution of the first single line script.
It may be doing the same thing in the second script as well but it is not seen
because the focusedObject is being placed in a variable.
Thanks,
John
On Oct 9, 2014, at 11:35 AM, J. Landman Gay <[email protected]> wrote:
> 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 | [email protected]
> HyperActive Software | http://www.hyperactivesw.com
>
>
> _______________________________________________
> use-livecode mailing list
> [email protected]
> Please visit this url to subscribe, unsubscribe and manage your subscription
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
