> I don't understand "but I can add put statements... NOT in the > getProp/setProp handlers". What do you mean?
When I was not able to set a breakpoint. I started to selectively include "Put xxx" so I could track the progress of app. I included put statement in both the handlers and in the setProp script. I do not see any output from the put statement that is in the setProp script. > Surely, stacks can get corrupted, but I have seen this happen only once > during the past few years. The reason was that the stack was moved from > Windows to Mac and opened, while text fields and scripts were somehow not > re-encoded. Ah ha. A new clue. This stack WAS moved to a windows system and brought back to mac! On 2012-01-15, at 9:35 AM, Mark Schonewille wrote: > Hi Mike, > > The debugger is not reliable to begin with, but there might be a valid reason > why you can't set a breakpoint, e.g. because that line is commented out. > > I don't understand "but I can add put statements... NOT in the > getProp/setProp handlers". What do you mean? > > It is possible that you have a character in your script that messes things > up, e.g. a NULL character or a return (rather than linefeed) character. Set > the script to empty and retype. Don't copy-paste. You might also use a hex > editor to find such characters and tools like BBEdit and TextWrangler allow > you to see invisible characters. > > Surely, stacks can get corrupted, but I have seen this happen only once > during the past few years. The reason was that the stack was moved from > Windows to Mac and opened, while text fields and scripts were somehow not > re-encoded. > > -- > Best regards, > > Mark Schonewille > > Economy-x-Talk Consulting and Software Engineering > Homepage: http://economy-x-talk.com > Twitter: http://twitter.com/xtalkprogrammer > KvK: 50277553 > > Become our partner in sales http://qery.us/1bq Start selling Color Converter > today. 20% commission! > > On 15 jan 2012, at 15:01, Michael Doub wrote: > >> I have a group "Pointer" that is made of 2 graphic objects. Within the >> script of group "Pointer", I have: >> >> setprop thecolor newcolor >> getProp thecolor >> setprop finger newloc >> >> I am not using them to set any persistent state but to control the color and >> location of the object itself. >> >> When this behaviour starts, I am not able to set a breakpoints, but I can >> add put statements and that handlers are getting called, but NOT in the >> getProp/setProp handlers. This app has been working for sometime now until >> I started making changes in totally unrelated areas of the code. I have >> gone back to the original working version twice now, trying to carefully >> make changes and testing trying to isolate what introduces the problem. >> >> I have also noticed that the debugger is off by several lines if you try >> single stepping. Can stacks get corrupted? >> >> -= Mike > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
