called stack does not come to top in standalone

[Emilio Gagliardi]

Greetings runrev gurus    It seems I'm finding lots of little  
*nuances* lately and I appreciate your patience with my emails.

I've been using the following code to open a stack from within a  
another stack:
go to stack /substack as topLevel

and the code has worked as expected in development.  Namely, the  
parent "window" is open and visible and when I click a button that  
calls the above code, a second window opens on top of the parent,  
which contains the substack.

It was working weeks ago sadly and now I tried to put it into the  
production environment and the behavior didn't work.  Furthermore,  
changing the mode (modal,toplevel,etc.) and decorations does not seem  
to make any difference.  That is in standalone mode, the substack is  
called, (I know this b/c the backdrop changes) but does not come to  
the top as it did in development, rather it opens below the parent  
window.  So, if the parent has a title bar I can drag it out of the  
way and reveal the substack.

Can anyone point me in the direction of how to force a stack to the  
top or why in standalone this is happening?

In a related vein, I tried setting the style of the substack to modal 
(go to stack /substack as modal), thinking it was ideal for forcing  
the user to complete the task on screen b4 moving on. However, when i  
did that, my dynamically generated buttons didn't appear!  This goes  
back to a previous problem I addressed in these forums which I solved  
by copying a hidden button and then pasting it.  For some reason,  
copy&paste does not seem to work in modal mode.

Cheers and thank you for your help.

Emilio