cursor temporarily vanishes on startup

[tech at paynesparkman.com]

I've for the most part solved my own problem.  I found that things which occur in a startup handler are supposed to occur before the stack is visible.  This means that not 
only should I not see the cursor until the startup handler is complete but, I shouldn't even see the stack until then.  My only confusion now is why I was able to see my stack 
during startup.  I made a sample stack with a startup handler which contained the line "wait 10 seconds".  When I double-click on that stack, I don't see it appear on my 
desktop until afer the 10 seconds has elapsed.  This problem did not occur when I switched engines.  It occurred when I switched from using openstack to startup.  I did this 
because I had added substacks to my stack and they were invoking the openstack handler in the main stack when they were opened.  This was not desirable behavior.  I 
now know that by putting openstack handlers in each of my substacks which don't include the command "pass openstack", the openstack message is trapped at the 
substack level and never gets passed to the main stack.

Rich Mooney

2/2/2004 12:21:46 PM, tech at paynesparkman.com wrote:

>Thanks for the tip Ray.  I haven't had any luck with it so far though.  I've noticed now that the problem is independent of whether I set the cursor to busy.  It dissappears 
even 
>when I leave it alone.  Something I forgot to mention in my first post is that everything works as it should when I open my stack in the editing environment and use the 
message 
>box to "send startup to this stack".
>
>Rich Mooney
>
>2/2/2004 10:19:21 AM, Ray Horsley <ray at linkitonline.com> wrote:
>
>>I've had the same problem under slightly different circumstances.  I'm 
>>sorry I don't have a cure-all solution, however, you might want to try 
>>experimenting with which window the cursor is on when you set it to 
>>"busy".  I've discovered this has an effect on whether the busy cursor 
>>appears or not.
>>
>>Ray Horsley
>>Developer, LinkIt! Software
>>
>>
>>On Monday, February 2, 2004, at 09:50 AM, tech at paynesparkman.com wrote:
>>
>>> I have the command "set the cursor to busy" in my startup handler.  Up 
>>> until around the 2.4.3 engine this would cause the cursor to turn into 
>>> a spinning beach ball while waiting
>>> for the configuration files to load.  Now the cursor disappears when 
>>> you pass it over the stack during startup then works normally after 
>>> startup is completed.  This makes it
>>> look more like it is locked up then loading configuration files.  Any 
>>> ideas what's going on here and how I can fix it?