My debugging this afternoon has reminded me of another circumstance where the debugger seems to ignore code and that's if you have a command in your script that doesn't flag an error but is not valid. Here's an example
insertObject "card", the long ID of card ID pCardID That doesn't cause an error when you compile and it doesn't cause a runtime error but when the statement is executed, the debugger just skips over it. It should be insertObject "card", the long ID of card ID pCardID of stack pstack I'm not sure why an error isn't flagged somewhere along the line but I spent a ridiculous amount of time debugging today before I noticed that I hadn't coded things correctly. Pete lcSQL Software <http://www.lcsql.com> On Wed, Jul 25, 2012 at 1:20 PM, Dr. Hawkins <doch...@gmail.com> wrote: > It's even stranger today. > > I keep seeing a behavior where it honors code breakpoints, but soft > breaks seem to send it into the trace . . . > > Gosh, maybe I should can and sell this :) > > _______________________________________________ > 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
