Re: Going crazy with closing a stack
On 02 Feb 2004, at 05:25, [EMAIL PROTECTED] wrote: Message: 7 Date: Mon, 02 Feb 2004 13:02:27 +0900 From: Doug Lerner <[EMAIL PROTECTED]> Subject: Re: Going crazy with closing a stack To: "[EMAIL PROTECTED],How to use Revolution" <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="US-ASCII" On 2/2/04 12:55 PM, "J. Landman Gay" <[EMAIL PROTECTED]> wrote: snip My main stack has one stack handler: on closeStack answer the target end closeStack Substack has one stack handler: on closeStack put "closing sub" end closeStack I click the closebox in the substack and "closing sub" appears in the message box. I never get an answer dialog. That's what I want to happen here too. :) [EMAIL PROTECTED] Why not use the closeStackRequest message? Greetings, WA ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Going crazy with closing a stack
That's almost what I ended up doing. Instead of running that stack as a substack, I made it its own stack and moved all the handlers except for openStack and closeStack elsewhere. It seems to be working this way. Thanks, dogu On 2/2/04 4:57 PM, "Frank Leahy" <[EMAIL PROTECTED]> wrote: > Doug, > > I'm guessing that other stacks of yours are getting closeStack > messages, right? If so then I'm pretty sure you're not getting a > closeStack because of something you're doing. Maybe you forgot to pass > menuPick, or pass some other message that is keep RunRev from sending > you the closeStack messages. > > Whatever it is, at this point I'd create a new stack, place just this > controller you're trying to use on it -- with no other scripts in the > stack except the closeStack -- and see if a closeStack handler gets > called. Then add your other scripts one at a time (or a bunch at a > time) until you see it stop getting called again. > > It's great to use the list as a sounding board, but sometimes the only > way to do debugging is to return to a zero baseline and actually do the > debugging. > > Good luck, > -- Frank > > On Monday, February 2, 2004, at 02:30 AM, > [EMAIL PROTECTED] wrote: > >> 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 > > ___ > use-revolution mailing list > [EMAIL PROTECTED] > http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Going crazy with closing a stack
Doug, I'm guessing that other stacks of yours are getting closeStack messages, right? If so then I'm pretty sure you're not getting a closeStack because of something you're doing. Maybe you forgot to pass menuPick, or pass some other message that is keep RunRev from sending you the closeStack messages. Whatever it is, at this point I'd create a new stack, place just this controller you're trying to use on it -- with no other scripts in the stack except the closeStack -- and see if a closeStack handler gets called. Then add your other scripts one at a time (or a bunch at a time) until you see it stop getting called again. It's great to use the list as a sounding board, but sometimes the only way to do debugging is to return to a zero baseline and actually do the debugging. Good luck, -- Frank On Monday, February 2, 2004, at 02:30 AM, [EMAIL PROTECTED] wrote: 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 ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Going crazy with closing a stack
I'm spending too much time on this one crazy closeStack message problem, so for the meantime I've put in the following work-around which is at least stable: * I have a button on the parent stack that is supposed to open/close the video grabber window-and-stack. In there I put: chatVideoPreviewOff revCloseVideoGrabber close stack vgName The closeChat message is still not being sent to the video grabber stack, but the stack closes. * In the video grabber stack I added on closeStackRequest -- block this stack from being closed from the window close button end closeStackRequest This blocks the stack from being manually closed, which is a little grody, but since the openStack handler doesn't get called reliably there is no choice. I must have users close the stack via the button in the parent stack. Interesting enough, even with this closeStackRequest handler here, the "close stack vgName" command above *does* close the stack. I wonder why the closeStackRequest doesn't block that as well. Strange all around. But at least this combination works - you can open and close the video grabber stack as much as you want by checking/unchecking the box in the parent stack. I'll come back to this issue again at another time. Thanks for all your suggestions. And if anybody has any extra ideas, please let me know! Thanks, doug ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Going crazy with closing a stack
On 2/2/04 1:24 PM, "J. Landman Gay" <[EMAIL PROTECTED]> wrote: > On 2/1/04 10:02 PM, Doug Lerner wrote: > >>> I click the closebox in the substack and "closing sub" appears in the >>> message box. I never get an answer dialog. >> >> >> That's what I want to happen here too. :) > > So there must be something else happening. Comment out all lines in both > stack's closestack handlers, with the exception of a single line in each > (pick one or write one that can stand independently and doesn't rely on > anything else.) If it works okay, then start adding pieces of the > handler back in until you reproduce the problem. Then tell us what that > piece is. That's why I put the "answer" command as the first line of the closeStack hander - to see if the handler was being called or not. But it's not. Except sometimes. And the sometimes seems to have something to do with the state of the video grabber window. Are there any extra commands that can tell us whether the video grabber window is even present or not? Also, what is that first (and undocumented) parameter to revInitializeVideoGrabber, as in the video stack example: revInitializeVideoGrabber the short name of this stack,"qt",iRect for? The docs only show 2 parameters. I think both these issues are connected somehow because I don't have similar problems when closing other stack windows. doug ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Going crazy with closing a stack
On 2/1/04 10:02 PM, Doug Lerner wrote: I click the closebox in the substack and "closing sub" appears in the message box. I never get an answer dialog. That's what I want to happen here too. :) So there must be something else happening. Comment out all lines in both stack's closestack handlers, with the exception of a single line in each (pick one or write one that can stand independently and doesn't rely on anything else.) If it works okay, then start adding pieces of the handler back in until you reproduce the problem. Then tell us what that piece is. -- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Going crazy with closing a stack
On 2/2/04 12:55 PM, "J. Landman Gay" <[EMAIL PROTECTED]> wrote: > On 2/1/04 8:20 PM, Thomas McGrath III wrote: > >> >> On Feb 1, 2004, at 9:05 PM, Doug Lerner wrote: >> >>> >>> I don't see how there could possibly be. This is a substack and inside >>> the >>> substack's script there is the closeStack handler. >> >> >> >> Doug, that was exactly what I had. A closeStack in a substack that I >> wanted to work when I closed the substack but instead I "think" the main >> stack was grabbing the closeStack and not the substack even though the >> closestack message was 'local' to the substack. > > If that's true, then it sounds like a bug. I just made a simple set of > test stacks, though, and I couldn't reproduce the behavior. There must > be something else going on. > > My main stack has one stack handler: > > on closeStack > answer the target > end closeStack > > Substack has one stack handler: > > on closeStack > put "closing sub" > end closeStack > > I click the closebox in the substack and "closing sub" appears in the > message box. I never get an answer dialog. That's what I want to happen here too. :) [EMAIL PROTECTED] ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Going crazy with closing a stack
On 2/1/04 8:20 PM, Thomas McGrath III wrote: On Feb 1, 2004, at 9:05 PM, Doug Lerner wrote: I don't see how there could possibly be. This is a substack and inside the substack's script there is the closeStack handler. Doug, that was exactly what I had. A closeStack in a substack that I wanted to work when I closed the substack but instead I "think" the main stack was grabbing the closeStack and not the substack even though the closestack message was 'local' to the substack. If that's true, then it sounds like a bug. I just made a simple set of test stacks, though, and I couldn't reproduce the behavior. There must be something else going on. My main stack has one stack handler: on closeStack answer the target end closeStack Substack has one stack handler: on closeStack put "closing sub" end closeStack I click the closebox in the substack and "closing sub" appears in the message box. I never get an answer dialog. -- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Going crazy with closing a stack
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" <[EMAIL PROTECTED]> wrote: On Sunday, February 1, 2004, at 10:02 PM, [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Going crazy with closing a stack
On 2/2/04 7:44 AM, "Frank Leahy" <[EMAIL PROTECTED]> wrote: > > On Sunday, February 1, 2004, at 10:02 PM, > [EMAIL PROTECTED] 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 [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Going crazy with closing a stack
On 2/2/04 6:50 AM, "Wilhelm Sanke" <[EMAIL PROTECTED]> wrote: > > On Mon Feb 2 Doug Lerner doug at webcrossing.com wrote: > >> >> When I close a stack in which the video grabber is embedded, I am >> trying to >> clean up as follows: >> >> (snip) >> >> BUT... even if I close the stack manually, the answer dialog doesn't even >> appear. >> >> The closeStack handler is just not being called. And it is a handler local >> to the stack itself! >> >> What might block the closeStack message from being sent to this stack >> handler? >> >> Thanks, >> >> doug > > > > Probably this is related to the problem Revolution has in handling > greater amounts of data. > > I have various stacks here that contain a larger number of controls on > one card. > > A stack with a card containing 1500 controls takes about 10 minutes to > close - on my G4 Powerbook with 667 MHz. > > Metacard closes the same stack immediately. This stack only has two controls on it - an image and a button. doug ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Going crazy with closing a stack
On 2/2/04 2:54 AM, "Robert Brenstein" <[EMAIL PROTECTED]> wrote: >> When I close a stack in which the video grabber is embedded, I am trying to >> clean up as follows: >> >> on closeStack >> global recordvideo >> answer "closing stack " & the short name of this stack >> put false into recordvideo >> revCloseVideoGrabber >> end closeStack >> >> Putting false into recordvideo should stop the repeat loop needed for QT, as >> per the sample stack and docs. revCloseVideoGrabber should close the video >> grabber. The answer command should at least acknowledge that the stack is >> being closed. >> >> BUT... even if I close the stack manually, the answer dialog doesn't even >> appear. >> >> The closeStack handler is just not being called. And it is a handler local >> to the stack itself! >> >> What might block the closeStack message from being sent to this stack >> handler? >> >> Thanks, >> >> doug > > I believe that the closeStack is sent as expected. However, the > engine is closing fast and the dialog is not showing up. It is known > that it does not wait for dialogs at that stage. If you want to pop a > dialog, use the closeStackRequest. JUst make sure to pass it or the > stack will never close. I know the local closeStack is not getting handled for other reasons though. For example, "false" is not get put into recordvideo and revCloseVideoGrabber is not getting called. doug ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Going crazy with closing a stack
On Sunday, February 1, 2004, at 10:02 PM, [EMAIL PROTECTED] 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. -- Frank ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Going crazy with closing a stack
On Mon Feb 2 Doug Lerner doug at webcrossing.com wrote: When I close a stack in which the video grabber is embedded, I am trying to clean up as follows: (snip) BUT... even if I close the stack manually, the answer dialog doesn't even appear. The closeStack handler is just not being called. And it is a handler local to the stack itself! What might block the closeStack message from being sent to this stack handler? Thanks, doug Probably this is related to the problem Revolution has in handling greater amounts of data. I have various stacks here that contain a larger number of controls on one card. A stack with a card containing 1500 controls takes about 10 minutes to close - on my G4 Powerbook with 667 MHz. Metacard closes the same stack immediately. Regards, Wilhelm Sanke ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Going crazy with closing a stack
When I close a stack in which the video grabber is embedded, I am trying to clean up as follows: on closeStack global recordvideo answer "closing stack " & the short name of this stack put false into recordvideo revCloseVideoGrabber end closeStack Putting false into recordvideo should stop the repeat loop needed for QT, as per the sample stack and docs. revCloseVideoGrabber should close the video grabber. The answer command should at least acknowledge that the stack is being closed. BUT... even if I close the stack manually, the answer dialog doesn't even appear. The closeStack handler is just not being called. And it is a handler local to the stack itself! What might block the closeStack message from being sent to this stack handler? Thanks, doug I believe that the closeStack is sent as expected. However, the engine is closing fast and the dialog is not showing up. It is known that it does not wait for dialogs at that stage. If you want to pop a dialog, use the closeStackRequest. JUst make sure to pass it or the stack will never close. Robert Brenstein ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Going crazy with closing a stack
When I close a stack in which the video grabber is embedded, I am trying to clean up as follows: on closeStack global recordvideo answer "closing stack " & the short name of this stack put false into recordvideo revCloseVideoGrabber end closeStack Putting false into recordvideo should stop the repeat loop needed for QT, as per the sample stack and docs. revCloseVideoGrabber should close the video grabber. The answer command should at least acknowledge that the stack is being closed. BUT... even if I close the stack manually, the answer dialog doesn't even appear. The closeStack handler is just not being called. And it is a handler local to the stack itself! What might block the closeStack message from being sent to this stack handler? Thanks, doug ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
