LiveCode Forums.

I have an application I am working on with several substacks.

The application starts with the main stack, then links to various instances of substacks.

Of course I could and probably should have handled this differently, however my main goal is to actually finish an application, good bad or ugly.

As part of the testing, I came across the following issue.

When the main stack calls a substack for the first time, the substack opens on top.

or above the main stack, which is what is needed, however once the user minimizes the substack upon a second call to that same substack the window opens in the background, not on top as I would like.

This issue is further complicated by other substacks that may also be open but minimized by the user.

I ran this test a number of times, and each time the same behavior is apparent.

once the substack is open and minimized upon a call from script to that substack the substack opens in the background.

I had a few thoughts about how to handle this however, my approach failed and did not address the issue of which substack should be set as active.

Interestingly, when the user clicks on the minimized substack it opens on top of other stacks and substacks, I wonder why that is?

anyway any thoughts suggestions, a treatise, or any other sublimations are always welcomed.

Have a Great Day.

Tim

Hi Tim,

I couldn't reproduce this on Windows - which OS are you running?

Jan Schenkel.

Janschenkel wrote:Hi Tim,

I couldn't reproduce this on Windows - which OS are you running?

Jan Schenkel.

Hi thanks for the reply,

I am using MAC OSX, 10.4.11

This is testing from the IDE, just to check I tested on a standalone and observed the same behavior,

I have not tested the standalone for windows to see if there is also the same behavior,

I have noticed some rather interesting changes in the 2.9 version for MAC OSX, some I have documented some are just weird little things that happen from time to time.

Aha, on a Mac I can make it happen as well; and I can't seem to find a real workaround. Hmm. Perhaps a trip to the Quality Center is in order.
http://quality.runrev.com

If you find things that are odd, and you can't find an explanation in the documentation, it's best to report them there - that way these issues are 'on the radar' for the engineers to look into.

Jan Schenkel.

Janschenkel wrote:Aha, on a Mac I can make it happen as well; and I can't seem to find a real workaround. Hmm. Perhaps a trip to the Quality Center is in order.
http://quality.runrev.com

If you find things that are odd, and you can't find an explanation in the documentation, it's best to report them there - that way these issues are 'on the radar' for the engineers to look into.

Jan Schenkel.

Yes, that is a good idea, I have some crash logs to add into the mix.

I will start with those, thanks, Tim