Re: Confusing Errors

2010-03-17 Thread Robert Brenstein
On 16.03.10 at 08:39 -0700 Dan Friedman apparently wrote: Mark (and others), Thanks for the info. Here's some more... global currentTarget global GlobalModeOption global gStudentXML global pMode set cursor to watch lock screen put the IDNumber of currentTarget into fPane

Confusing Errors

2010-03-16 Thread Dan Friedman
Greetings, My standalone is is throwing some errors that I can't seem to figure out. The errors are being thrown because I included the Bug Reports option when I generated the standalone. Here is the error:

Re: Confusing Errors

2010-03-16 Thread Mark Schonewille
Hi Dan, The Line Num may be zero because your stack is protected by a password. Sometimes the debugging tools just don't work properly and can't find the offending line. It also happens that the actual error occurs in a Revolution script library, which the debugger can't figure out.

Re: Confusing Errors

2010-03-16 Thread Richard Gaskin
Dan Friedman wrote: ... - Executing at 5:44:49 PM on Monday, March 15, 2010 Type: Object: does not have this property Object: button 'Save' of card 'card id 1002' of stack 'EditComment' Line: put the

Re: Confusing Errors

2010-03-16 Thread Mark Wieder
Richard- Tuesday, March 16, 2010, 8:16:22 AM, you wrote: Because the error reporting is using the same engine that encountered the error, sometimes getting error info in Rev is like doing watch repair where the only tool you have is another watch. ;) ...and that one's broken, too... --

Confusing Errors

2010-03-16 Thread Dan Friedman
Mark (and others), Thanks for the info. Here's some more... The stack is not password protected. I did use normal quotes (it wouldn't compile if I hadn't), the debugger presents quotes as single-quotes in it's errors. And, currentTarget is a valid pointer to a field. The stack wouldn't

Re: Confusing Errors

2010-03-16 Thread Sarah Reichelt
on mouseUp  global activeRCMStudentIDNum  global currentReportIDNum  global currentTarget  global GlobalModeOption  global gStudentXML  global pMode  set cursor to watch  lock screen  put the IDNumber of currentTarget into fPane  --this is where it's tripping I would guess that

Re: Confusing Errors

2010-03-16 Thread Kay C Lan
On Tue, Mar 16, 2010 at 11:39 PM, Dan Friedman d...@clearvisiontech.com wrote: As you can see, it's the first [evaluated] line in the script.  If it matters, this is a modal dialog.  Also noteworthy, is that I can't repeat this error.  These reports are coming from users.  Also, they are