Context-free error messages during debugging

Mark Schonewille m.schonewille at
Sat Oct 14 19:58:48 EDT 2006

Hi Graham,

You could adjust the message box to throw errors instead of  
displaying them in its lower field, but it is probably easier to  
create your own message box and save that as a plugin. Just make a  
palette window with a field and the following script:

on enterInField
   do me
end enterInField

This kind of errors (Chunk: can't find card) occurs after referring  
to a property of a nonexisting card, such as

put the bla of cd x
put the name of btn x of cd y

Sorry, there are too many possibilities to give an exact cause of the  
error, but I hope this helps anyway.




Consultancy and Software Engineering

Get your store on-line within minutes with Salery Web Store software.  
Download at

Op 15-okt-2006, om 1:31 heeft Graham Samuel het volgende geschreven:

> One of the most irritating aspects of debugging in Rev (or in  
> Galaxy for that matter) is that there are circumstances (usually  
> when a rev app starts up) when you can get an error in the message  
> box, such as
>> Message execution error:
>> Error description: Chunk: can't find card
> with no other context given, i.e. the IDE's debugging display is  
> not invoked. This seems absurd, since the engine can't have  
> interpreted the script all without knowing which line of which  
> script it was executing, as well as the name of the object it can't  
> find (in the example above): so this info could and should (IMO) be  
> provided to the developer.
> Does anyone know
> a) exactly under what conditions this type of error occurs;
> b) if there is a workaround (apart from simply stepping through  
> every line of script) to find the context of the error.
> Graham

More information about the use-livecode mailing list