Boy I sure do! But it is an issue with doing something stupid like trying to make changes to code and compile it while I am still debugging using PowerDebug. Don't know if it would happen with the normal debugger so I cannot say it is power debug, and anyway the proper response to compiling code during debugging should be, "Don't do that!" :-)
Also, having tabs open in GLX2 for a stack that has been removed from memory is another great way to lock up the IDE. Again, not sure if the stock editor would behave the same way. I just throw that out there as vectors on IDE lockups that some may not have considered yet. Also, I think Mark Wieder may have addressed this one in the latest release of GLX2. Bob On Mar 6, 2012, at 9:25 AM, J. Landman Gay wrote: > On 3/6/12 6:57 AM, Ken Corey wrote: > >> That way, when I bork the IDE, or do something silly with 'answer' or >> 'modal' or whatever, I am 10 seconds away from restarting LiveCode and >> being right where I was. This happens often enough that IMNSHO the >> 'Apply' button should simply be removed. > > Removing Apply would seriously affect my work flow. I routinely try out new > things and if I bork it too much to backtrack, I revert the stack. I save > manually immediately after every change I want to keep. That's often enough > that I rarely lose anything -- but I don't seem to have much trouble with the > IDE locking up. I almost never experience it. > > -- > Jacqueline Landman Gay | jac...@hyperactivesw.com > HyperActive Software | http://www.hyperactivesw.com > > _______________________________________________ > 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
