standalone application problem

Michael Robinson robinsongroup at
Sat Jul 8 11:30:01 EDT 2006

I see what you mean, but it did work in the preopenstck handler until  
now, changed it to openstack handler but it still does not work the  
first time.
Any other thoughts

On Jul 7, 2006, at 8:34 PM, J. Landman Gay wrote:

> Michael Robinson wrote:
> >
> > I will try to give you more information here it is -
> > you build the standalone
> > start the application
> > after it is opened you then either create a new file (cloning of a
> > sub-stack) or open a file you already created. Either way when  
> the file
> > opens, it opens another sub-stack as a drawer. The command  
> originates
> > from the stack you either cloned or opened in the preOpenstack  
> handler.
> > The sub-stack that was cloned or opened makes documents.
> >
> > So - the whole thing works after you open and close it a few  
> times, but
> > not from the get-go like it has sense version 1.1.1
> When the preOpenStack message is sent, the stack has not been drawn  
> on screen yet. So I'm not sure how you could open a drawer on a  
> stack that isn't there. Since you say it used to work, maybe the  
> stack was forced into visibility prematurely (which is just a wild  
> guess.) At any rate, what happens if you move the drawer command to  
> the openStack handler instead? The openStack handler is sent after  
> the stack is already open and the window has been created. You need  
> a visible window to hang a drawer from.
> I may still be confused about the order of the actions you're  
> executing, so maybe this won't work, but it is worth a try.
> -- 
> Jacqueline Landman Gay         |     jacque at
> HyperActive Software           |
> _______________________________________________
> use-revolution mailing list
> use-revolution at
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:

More information about the Use-livecode mailing list