Hmmm... does the modal stack have the destroystack property set to true? I wonder if not doing so leaves it in memory and it remains the default stack? Just guessing...
Bob On Jan 31, 2011, at 11:36 PM, Peter Haworth wrote: > I still have no idea why this is happening but I have fixed it by setting the > defaultStack to the topStack immediately on return form the modal dialog. > > I'm now chasing down another problem. I have a mouseUp and a mouseDoubleUp > handler for the same control. When I double click, the mouseUp handler is > triggered, not the mouseDoubleUp. How do suppress the mouseUp processing in > favour of the mouseDoubleUp? > > Pete Haworth > > > > > > > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
