The short version is I don't know. There must be something but I can't tell what it is.
I'm closing cloned stacks but that shouldn't matter. Also, if I navigate to different cards on one of the still remaining stacks the messages happen and the user is prompted for saving a stack that needs it. If I don't navigate then a menu Quit just quits and never prompts the user. Bill On Monday, November 19, 2007, at 07:29AM, "Richard Gaskin" <[EMAIL PROTECTED]> wrote: >Bill Vlahos wrote: > >> I think these problems are bugzilla'd originally in 4994 and then also >> in 5362 (which is marked as a duplicate of 4994). However, the >> workaround does not work for me. >... >>> In your stack which is experiencing difficulty quitting, which >>> messages are you trapping and how are those messages handled? >> That's the problem. If I am closing a window I successfully get >> prompted for the save and if I say YES then everything works >> correctly. However, if I say NO then it correctly doesn't save but >> blocks subsequent trappings for other open stack windows. > >What differs between your app and those in which the noted workaround works? > >-- > Richard Gaskin > Managing Editor, revJournal > _______________________________________________________ > Rev tips, tutorials and more: http://www.revJournal.com >_______________________________________________ >use-revolution mailing list >use-revolution@lists.runrev.com >Please visit this url to subscribe, unsubscribe and manage your subscription >preferences: >http://lists.runrev.com/mailman/listinfo/use-revolution > > _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
