Chipp,
The bug has been reported already:
http://quality.runrev.com/qacenter/show_bug.cgi?id=3086
Best,
Mark
--
Economy-x-Talk
Consultancy and Software Engineering
http://economy-x-talk.com
http://www.salery.biz
Get your store on-line within minutes with Salery Web Store software.
Download at http://www.salery.biz
Op 6-feb-2007, om 5:57 heeft Chipp Walters het volgende geschreven:
Hi all,
I've run into a really weird bug which I'm not sure how to get around.
It involves invoking the debugger from a background group script from
a card which the script has been placed on.
It's basically a very simple thing to describe. I want to be able to
set a breakpoint in a background group script and have it enter debug
mode. I find I can do this ONLY when I'm on the originating card from
where the group was created. IOW, any OTHER card where the group
resides, will execute the script, but not invoke the debugger. It just
'jumps' right over a breakpoint statement.
I'm using 2.7.4 and was hoping someone else out there would verify,
and/or suggest a work around.
You can run the test stack by putting below into the msg box:
go URL "http://www.gadgetplugins.com/chippstuff/GroupDebugBug.rev";
TIA,
Chipp
_______________________________________________
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
