Right.
I'm in the habit of just reporting the system bugs when I come across them.
Sometimes they get fixed, other times no.
-
--
Mark Wieder
ahsoftw...@gmail.com
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/Debugging-the-IDE-tp4709922p4710088
Already pointed it out to the powers that be, and they acknowledged it was an
issue. I was thinking that since dev stacks don't throw errors when
gRevRevelopment is set to false, devs might use this as a poor man's
"try/catch/donothing" mechanism so they do not have to check for conditions
whic
ffect enough people to warrant
assigning resources to...
-
--
Mark Wieder
ahsoftw...@gmail.com
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/Debugging-the-IDE-tp4709922p4710067.html
Sent from the Revolution - User mail
Mark Wieder write:
> On 11/03/2016 05:54 PM, Richard Gaskin wrote:
>> Bob Sneidar wrote:
>>> To my horror I am finding a number of errors where a handler is
>>> being called that didn't exist, but it never shows up because if
>>> gRevDevelopment is false, plugins silently fail.
>>
>> How?
>>
>> P
On 11/03/2016 05:54 PM, Richard Gaskin wrote:
Bob Sneidar wrote:
...I set the global gRevDevelopment to true so I can step through
the scripts.
That should not be necessary.
See below.
To my horror I am finding a number of errors where a handler is being
called that didn't exist, but i
Bob Sneidar wrote:
> ...I set the global gRevDevelopment to true so I can step through
> the scripts.
That should not be necessary.
> To my horror I am finding a number of errors where a handler is being
> called that didn't exist, but it never shows up because if
> gRevDevelopment is false, p
Hi all.
I'm going to throw this out there, and see if I get a bite. I have been
spending a good part of the day trying to debug a plugin, I won't say which. To
do this I set the global gRevDevelopment to true so I can step through the
scripts. To my horror I am finding a number of errors where
