Bob Sneidar <bobs@...> writes: > > Actually, Mark Weider has done a lot to make GLX2 stable and better.
Thanks! The current version seems to be working > really well. To my knowledge, PowerDebug has never been the source of any issues I have run into, but my > memory is really bad so take that with a grain of salt. The issues I have had were also present in the vanilla > debugger if I recall. I will go so far as to say that many of the features in the built-in editor and debugger > were the result of Jerry's pioneering work in GLX2. PowerDebug is just the GLX2 debugger broken out as a > separate plugin (correct me if I am wrong). I originally broke the debugger out as a separate plugin because mixing the code together was starting to get hopelessly complicated. And I wanted to have the debugger work with Remo. There are only a few points of contact between the script editor and the debugger, so it was easy enough to pull these out into an api. But PowerDebug rapidly took on a life of its own with added features and more robustness, especially as it evolved the ability to debug standalone applications. > > I like PowerDebug for a few reasons, not the least of which is a hotkey for step over, into and what have you. I > especially like usign the spacebar to step through code. I think their variable inspector is really well > done as well. Being able to view the contents of an array has been especially useful to me and is primarily > why I even use the LC arrays after becoming so used to numbered key style arrays. I also like the way tabs are > managed, and the bread crumbs feature is genius. My favorite features of GLX2 are breadcrumbs, handler links, and folders. I really miss all those when I have to work in the IDE's script editor. OTOH, the IDE has better search capabilities. > The problem of course, with this kind of editor and debugger, as Jerry has pointed out in the past, is that > because it is done entirely in LC, the potential for breaking it when new versions of LC come out that make > changes to the engine is always a factor. <groan> Quite right. And the changes, when they come, aren't usually documented, forcing a mad scramble and regression test with each new release. </groan> Back on topic, the soft breakpoints set in the editor are stored as custom properties of the target stack and sometimes don't align properly any more with the script text. Recompiling the script *should* fix this, but doesn't always do that. Removing the custom property and setting the breakpoints again should work. -- Mark Wieder _______________________________________________ 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
