> The non-debug mode of the debugger is much needed for globals > debugging. Alas it doesn't do arrays (unless you get a new > mod release I mentioned earlier...)
sorry - non related - I "qui pro quo"'d Mark and my brain didn't register something! No rant or anything meant... I just spent a big part of the day working on the mc variable watcher and finishing some workflow issues with my old mc script editor... is there anyone still using Metacard? cheers Xavier > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of MisterX > Sent: Wednesday, November 09, 2005 17:07 > To: 'How to use Revolution' > Subject: RE: Buggy debugger -- solved? > > > > > On Behalf Of Mark Schonewille > > > In my view, the debugger should never just drop out of > debug mode. It > > should give some feedback to tell the user why it can't continue > > debugging. If we can figure out what happened with your > stack, maybe > > RunRev can add some proper error handling in the deugger. > Mark, > > The non-debug mode of the debugger is much needed for globals > debugging. Alas it doesn't do arrays (unless you get a new > mod release I mentioned earlier...) > > Now, I tested Timothy's problem in a stack with a background > inserted the breakpoint. Launched the handler. The script > editor opened but no debugging going to work!!! oops... > > Good call!!! > > The debugging works ok in the 2.5 Rev version. > > I would bugzill'it! > > cheers > Xavier > http://monsieurx.com/taoo > > _______________________________________________ > 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
