Eric- Tuesday, July 12, 2005, 12:31:48 AM, you wrote:
EC> There is another case where the debugger does not work: when the EC> stack name begin with "rev". EC> It's not a bug but a feature, an annoying feature when you write EC> plugins ;-) Take a look at the trace handler in the debugger button of the revLibrary stack. It's revTargetStack() that's the culprit. Comment out the true part of the conditional and leave everything after the else - makes life bearable again. NB: most of the time you want the default behavior - *not* tracing through the rev stacks - as the debugger will trip over itself in various ways. However, being able to drill down into the rev libraries themselves is essential if you're developing plugins or working with the libraries themselves. Caveat Revver. -- -Mark Wieder [EMAIL PROTECTED] _______________________________________________ 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
