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
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
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
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
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
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
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
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
