Yeah - and what a nightmare to debug! Not sure if it does this in Rev IDE but any bug or event that causes something to be put into the messagebox - triggers the resumeStack again which can then cause infinite loops - goto block that....
2008/6/2 Mark Schonewille <[EMAIL PROTECTED]>: > Hi david, > > I'd trap the resumeStack message, sometimes the (pre)openStack message, in > a front script. > > -- > Best regards, > > Mark Schonewille > > Economy-x-Talk Consulting and Software Engineering > http://economy-x-talk.com > http://www.salery.biz > > Benefit from our inexpensive hosting services. See > http://economy-x-talk.com/server.html for more info. > > > On 1 jun 2008, at 01:45, David Bovill wrote: > > Its been a while since I've done this... what's the best way to trap for >> this? Do I need a front script (in case the stack blocks a message) - or >> can >> I intercept and pass a Rev IDE specific message? >> > > _______________________________________________ > use-revolution mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution > _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
