When I change the resizeable property to be false then it behaves properly.
It will then go toplevel. Weird
On Fri, May 6, 2011 at 2:50 PM, william humphrey wrote:
> More experiments. It has nothing to do with the drawer stack. I have the
> stack by itself and it won't "toplevel"
>
>
> On Fri, M
More experiments. It has nothing to do with the drawer stack. I have the
stack by itself and it won't "toplevel"
On Fri, May 6, 2011 at 2:48 PM, william humphrey wrote:
> I tried toplevel stack stackname and that works for every stack except one
> which has a MacOS drawer hanging off the side.
>
I tried toplevel stack stackname and that works for every stack except one
which has a MacOS drawer hanging off the side.
On Fri, May 6, 2011 at 2:15 PM, Phil Davis wrote:
> Try "toplevel" instead of "go" - that will bring the stack to the front.
>
> Phil
>
>
>
> On 5/6/11 10:08 AM, william hump
Try "toplevel" instead of "go" - that will bring the stack to the front.
Phil
On 5/6/11 10:08 AM, william humphrey wrote:
I have a livecode app with many stacks. One of the stacks has a drawer
(MACOS) on the side. When you "GO" that stack it becomes active but remains
in the background with th
I have a livecode app with many stacks. One of the stacks has a drawer
(MACOS) on the side. When you "GO" that stack it becomes active but remains
in the background with the other stacks on top of it. Can anybody offer some
suggestions on how to get this stack on it's drawer to be on top when you g
