Going back to this issue, I tried Richard’s suggestion and it didn’t work in LC
7.0.1. I isolated the problem in a little stack and reported it as a bug
(13958), but it’s not yet confirmed. I believe I detected an anomaly in the IDE
and a different one in a standalone, but they are probably diff
On Nov 3, 2014, at 10:26 AM, Richard Gaskin wrote:
> Graham Samuel wrote:
> > If I am keying in a field in an ordinary stack window and I stop
> > to do something on a palette, I had hoped that the focusedObject
> > would remain in the ordinary stack - however it turns out that
> > the focusedObje
Richard. Wrote:
> If just buttons remember to turn off the traversalOn property and you
> should be fine.
This makes sense as a pop up stack menu is just this and it doesn't take focus
from the underlying field.
James
___
use-livecode mailing lis
I think if the pallet begins with “rev” then it is treated as a development
object, and thus will not affect the focusedObject, but that is off the top of
my head from reading all the proper posts on the matter.
Bob S
> On Nov 2, 2014, at 15:25 , Graham Samuel wrote:
>
> Another probably du
Graham Samuel wrote:
> If I am keying in a field in an ordinary stack window and I stop
> to do something on a palette, I had hoped that the focusedObject
> would remain in the ordinary stack - however it turns out that
> the focusedObject is now the visible card of the palette. Does
> this mean t
...
Craig Newman
-Original Message-
From: Graham Samuel
To: How to use LiveCode
Sent: Sun, Nov 2, 2014 6:25 pm
Subject: Palettes and the selectedObject
Another probably dumb question.
If I am keying in a field in an ordinary stack window and I stop to do
something
on a pale
Another probably dumb question.
If I am keying in a field in an ordinary stack window and I stop to do
something on a palette, I had hoped that the focusedObject would remain in the
ordinary stack - however it turns out that the focusedObject is now the visible
card of the palette. Does this me
