Going crazy with closing a stack

[Doug Lerner]

Thanks for your note, Tom.

Unfortunately, I can't move this stuff into the startup and shutdown
handlers because this is just one of several stacks that are open while
running the app and doesn't take place at shutdown.

doug

On 2/2/04 10:08 AM, "Thomas McGrath III" <3mcgrath at adelphia.net> wrote:

> Doug,
> 
> I was having problems with the closeStack as well and it seems everyone
> said it must be something I was doing. Well, usually it is.;-)
> 
> But once I put my close down stuff into the on shutDown and my start up
> stuff into on StartUp everything now gets set and handled and works
> great.
> 
> It seems to me, since you can put closeStack in a stack and in a
> substack and elsewhere that it may not be as pure as is stated. I mean
> startup is just that and only goes off on startup and shutdown is just
> that and only goes off on shutdown. But preOpenStack and OpenStack and
> closestackrequest etc. seem to be upwardly mobile. I mean they work
> best handling upstream stuff.
> 
> Of course I haven't a clue and will probably get reamed but I tell you
> once I moved my stuff into the startup and shutdown handlers they
> finally got called as expected and things then worked great. One
> problem though, I could not debug the startup in the IDE for some
> reason. I put in a break and it never showed but in the standalone
> things were smooth.
> 
> FWIW
> 
> Tom
> 
> On Feb 1, 2004, at 6:31 PM, Doug Lerner wrote:
> 
>> On 2/2/04 7:44 AM, "Frank Leahy" <frank at backtalk.com> wrote:
>> 
>>> 
>>> On Sunday, February 1, 2004, at 10:02  PM,
>>> use-revolution-request at lists.runrev.com wrote:
>>> 
>>>> A stack with a card containing 1500 controls takes about 10 minutes
>>>> to
>>>> close - on my G4 Powerbook with 667 MHz.
>>> 
>>> If you are doing something with those controls when you close the
>>> stack
>>> (e.g. moving them, or resetting any values), that can take a very long
>>> time.
>>> 
>>> Either way, try setting lock screen and lock messages in your
>>> closeStack handler and see if that speeds things up.
>> 
>> My problem doesn't have anything to do with excessive controls. There
>> are
>> just two in the stack. I am sure the closeStack handler itself is just
>> not
>> being run, even when manually closing the stack. The
>> revCloseVideoGrabber
>> isn't happening, which is what got me started on this.
>> 
>> doug
>> 
>> _______________________________________________
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
>> http://lists.runrev.com/mailman/listinfo/use-revolution
>> 
>> 
> 
> Thomas J. McGrath III
> SCS
> 1000 Killarney Dr.
> Pittsburgh, PA 15234
> 412-885-8541
> 
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution