5.0.2 startup woes

[Mike Bonner]

There seems to be a timing problem going on in this case. The same question
was in the forums and a workaround is to set up a separate handler to pick
the browse tool and then do a send in time to call it so taht the browse
tool choice ends up at the end of the queue.

There were problems whether the browse tool was picked in preopenstack or
openstack.  When the send in time was used in the openstack handler they
were able to get it to work with 'send "mybrowsetoolhandler" to me in 2
milliseconds'  Hopefully they'll fix this weirdness with the next update.