no such object in step by step debugger

Mark Schonewille m.schonewille at economy-x-talk.com
Fri Nov 7 14:33:54 EST 2008


Hi Jacques,

This has nothing to do with the debugger. The syntax

   put field theField into thevar

is incorrect and should be

   put the text of theField into thevar

--
Best regards,

Mark Schonewille

Economy-x-Talk Consulting and Software Engineering
http://economy-x-talk.com
http://www.salery.biz
Dutch forum: http://runrev.info/rrforum/

Benefit from our inexpensive hosting services. See http://economy-x-talk.com/server.html 
  for more info.

On 7 nov 2008, at 20:04, Jacques Hausser wrote:

> Hello,
> I was away from Revolution for a while (to many other things to do)  
> but now I'm just retired (yes!!!) and at least I have time to work a  
> bit more on some applications I planned to do... and I discovered a  
> strange thing with the new debugger.
> Forgive me if it is known already (but in this case answer  
> nevertheless directly, many thank, I was unable to find something  
> about this problem on the list).
> I have a stack's custom property called CurrentField, containing the  
> short name of a field. In the stack script I have something like:
>
> put the currentField of me into theField
> put word 2 of theField into numvar
> -- here some stuff with numvar
> put field theField into thevar
> -- here some stuff with the content of the field (thevar)
>
> Well. If I put a breakpoint on the last line of this script,  
> everything is OK, numvar and thevar both contain what I want. BUT if  
> I put my breakpoint on the first line, and progress step by step, I  
> get an error "chunk: no such object" at the "put field theField" line.
> If I change my mind and put the long name of the field in the  
> currentfield, everything is OK, but it is just boring and more heavy  
> to parse to get my information back.
> The same problem seems to occur with any objects designed by their  
> short name. The defaultStack is the good one (mine). I got this  
> problem with Revolution 3 on a Mac Intel with OS X 10.5.5
> I think it's not a fair behaviour for a debugger, but perhaps it is  
> not orthodoxal to invoke objects by their short name...
>
> Thank you for advice
>
> Jacques




More information about the use-livecode mailing list