Re: Debugging plugins
Pete- Wednesday, January 14, 2015, 10:18:46 AM, you wrote: If I understand this correctly, if a stack name begins with rev and gRevDevelopment is false, any runtime errors in it are ignored? That's any stack, not just IDE stacks? That is correct. I don't suppose this would also enable some way to trap runtime errors and report info about them, would it? I'm not following that. Runtime errors *are* trapped, unless I'm misunderstanding you, which I suppose is pretty obvious. -- -Mark Wieder ahsoftw...@gmail.com This communication may be unlawfully collected and stored by the National Security Agency (NSA) in secret. The parties to this email do not consent to the retrieving or storing of this communication and any related metadata, as well as printing, copying, re-transmitting, disseminating, or otherwise using it. If you believe you have received this communication in error, please delete it immediately. ___ 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
Re: Debugging plugins
Thanks Mark. What I mean is, if errors in the revxxx stack are ignored (I assume that means runtime errors?), is there some other way that the stack can determine that they happened so they can be handled more gracefully? Kinda like an error in a try/catch loop. Pete lcSQL Software http://www.lcsql.com Home of lcStackBrowser http://www.lcsql.com/lcstackbrowser.html and SQLiteAdmin http://www.lcsql.com/sqliteadmin.html On Wed, Jan 14, 2015 at 1:30 PM, Mark Wieder mwie...@ahsoftware.net wrote: Pete- Wednesday, January 14, 2015, 10:18:46 AM, you wrote: If I understand this correctly, if a stack name begins with rev and gRevDevelopment is false, any runtime errors in it are ignored? That's any stack, not just IDE stacks? That is correct. I don't suppose this would also enable some way to trap runtime errors and report info about them, would it? I'm not following that. Runtime errors *are* trapped, unless I'm misunderstanding you, which I suppose is pretty obvious. -- -Mark Wieder ahsoftw...@gmail.com This communication may be unlawfully collected and stored by the National Security Agency (NSA) in secret. The parties to this email do not consent to the retrieving or storing of this communication and any related metadata, as well as printing, copying, re-transmitting, disseminating, or otherwise using it. If you believe you have received this communication in error, please delete it immediately. ___ 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
Re: Debugging plugins
Pete- Wednesday, January 14, 2015, 1:50:53 PM, you wrote: Thanks Mark. What I mean is, if errors in the revxxx stack are ignored (I assume that means runtime errors?), is there some other way that the stack can determine that they happened so they can be handled more gracefully? Kinda like an error in a try/catch loop. You could patch the IDE. There's a handler in one of the frontscript libraries (I forget the details off the top of my head) that determines whether or not to pass the error on for handling. -- -Mark Wieder ahsoftw...@gmail.com This communication may be unlawfully collected and stored by the National Security Agency (NSA) in secret. The parties to this email do not consent to the retrieving or storing of this communication and any related metadata, as well as printing, copying, re-transmitting, disseminating, or otherwise using it. If you believe you have received this communication in error, please delete it immediately. ___ 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
Re: Debugging plugins
On Wed, Jan 14, 2015 at 11:22 AM, J. Landman Gay jac...@hyperactivesw.com wrote: The simplest thing might be to temporarily rename your plugin without the rev prefix while you're working on it. This gives me the opportunity to use my favorite phrase from an Apple commercial: What, was I in thinking jail? Apart from how much of a pain it is to rename a stack with behavior buttons in it, this was straightforward and works perfectly. thanks! ___ 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
Re: Debugging plugins
Thanks to those who suggested Script Debug Mode and breakpoint. In plugins, neither of those allows setting a breakpoint that will work. global gRevDevelopment;put true into gRevDevelopment enables breakpoints in plugins, but in 6.7 at least seems to completely break the variable panel in the debugger. On Thu, Jan 8, 2015 at 6:51 PM, Mark Talluto use...@canelasoftware.com wrote: On Jan 5, 2015, at 8:16 AM, Geoff Canyon gcan...@gmail.com wrote: I have a vague recollection of there being a way to get breakpoints to work in rev stacks. I thought it was a preference setting, but I don't see it. Anyone know what the setting/property is for that? There is a menu item labeled‘Script Debug Mode’ in the ‘Development’ drop down of the LiveCode menus. Best regards, Mark Talluto livecloud.io canelasoftware.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
Re: Debugging plugins
Geoff- Wednesday, January 14, 2015, 8:26:15 AM, you wrote: global gRevDevelopment;put true into gRevDevelopment enables breakpoints in plugins, but in 6.7 at least seems to completely break the variable panel in the debugger. Yeah. What Jacque said. The downside of setting gRevDevelopment to true is that bugs in the IDE stacks are no longer ignored. -- -Mark Wieder ahsoftw...@gmail.com This communication may be unlawfully collected and stored by the National Security Agency (NSA) in secret. The parties to this email do not consent to the retrieving or storing of this communication and any related metadata, as well as printing, copying, re-transmitting, disseminating, or otherwise using it. If you believe you have received this communication in error, please delete it immediately. ___ 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
Re: Debugging plugins
On 1/14/2015 10:26 AM, Geoff Canyon wrote: Thanks to those who suggested Script Debug Mode and breakpoint. In plugins, neither of those allows setting a breakpoint that will work. global gRevDevelopment;put true into gRevDevelopment enables breakpoints in plugins, but in 6.7 at least seems to completely break the variable panel in the debugger. The simplest thing might be to temporarily rename your plugin without the rev prefix while you're working on 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
Re: Debugging plugins
If I understand this correctly, if a stack name begins with rev and gRevDevelopment is false, any runtime errors in it are ignored? That's any stack, not just IDE stacks? I don't suppose this would also enable some way to trap runtime errors and report info about them, would it? Pete lcSQL Software http://www.lcsql.com Home of lcStackBrowser http://www.lcsql.com/lcstackbrowser.html and SQLiteAdmin http://www.lcsql.com/sqliteadmin.html On Wed, Jan 14, 2015 at 9:57 AM, Mark Wieder mwie...@ahsoftware.net wrote: Geoff- Wednesday, January 14, 2015, 8:26:15 AM, you wrote: global gRevDevelopment;put true into gRevDevelopment enables breakpoints in plugins, but in 6.7 at least seems to completely break the variable panel in the debugger. Yeah. What Jacque said. The downside of setting gRevDevelopment to true is that bugs in the IDE stacks are no longer ignored. -- -Mark Wieder ahsoftw...@gmail.com This communication may be unlawfully collected and stored by the National Security Agency (NSA) in secret. The parties to this email do not consent to the retrieving or storing of this communication and any related metadata, as well as printing, copying, re-transmitting, disseminating, or otherwise using it. If you believe you have received this communication in error, please delete it immediately. ___ 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
