OIC that’s important. Try/Catch allows continued execution for what would
otherwise be fatal errors, errorDialog does not. Is that what you are saying?
Bob S
On Nov 20, 2014, at 09:25 , Richard Gaskin
mailto:ambassa...@fourthworld.com>> wrote:
Try/catch is also useful, but for different purpo
Bob Sneidar wrote:
>> On Nov 20, 2014, at 08:26 , Richard Gaskin wrote:
>>
>> Bob Sneidar wrote:
>>
>> > In FoxPro you could simply create a handler which got triggered by
>> > errors then check an internal code for what the most recent error
>> > was, then make a switch statement to handle all t
Oh cool! I asked this same thing years ago, and got back from everyone, “Just
use try/catch.”
I’ll look into that.
Bob S
> On Nov 20, 2014, at 08:26 , Richard Gaskin wrote:
>
> Bob Sneidar wrote:
>
> > In FoxPro you could simply create a handler which got triggered by
> > errors then chec
Bob Sneidar wrote:
> In FoxPro you could simply create a handler which got triggered by
> errors then check an internal code for what the most recent error
> was, then make a switch statement to handle all the pertinent errors
> for your project. The normal error message display was suppressed so
Don’t you also need the card reference, or is that implied?
Bob S
On Nov 19, 2014, at 13:17 , Richmond
mailto:richmondmathew...@gmail.com>> wrote:
put the lines of fld "ERRS" of stack "ERRORS" into cErrorsList of card 1 of
stack "revErrorDisplay"
_
trigger another
> stack with Custom notes and warnings.
>
> Thanks a lot again, Jacque.
>
> Al
>
>
>
>
>
>
> --
> View this message in context:
> http://runtime-revolution.278305.n4.nabble.com/Meaningful-and-verbo
On 11/19/2014, 3:17 PM, Richmond wrote:
HOWEVER, when I tried this:
put fld "ERRS" of stack "ERRORS" into cErrorsList of card 1 of stack
"revErrorDisplay"
Well, you can't "put" anything into a custom property, those have to be
set. And you need "the": "set the cErrorsList of cd 1 of..."
p
On 11/19/2014, 2:47 PM, Alejandro Tejada wrote:
After my current headache dissapears, I will study
how these error messages could trigger another
stack with Custom notes and warnings.
The easiest way is to write an errorDialog handler and trap the error
that way. You'd need the handler in ever
You can set up a stack called, for instance "ERRORS" with a field called
"ERRS"
and a button with this script:
on mouseUp
put the cErrorsList of card 1 of stack "revErrorDisplay" into fld
"ERRS" of stack "ERRORS"
end mouseUp
what is interesting is that the resulting list contains quite a f
essage in context:
http://runtime-revolution.278305.n4.nabble.com/Meaningful-and-verbose-error-messages-in-LiveCode-tp4686019p4686049.html
Sent from the Revolution - User mailing list archive at Nabble.com.
___
use-livecode mailing list
use-livecode@list
On 11/19/2014, 1:31 PM, Alejandro Tejada wrote:
Does exist a method to show our own custom
warnings or messages when LiveCode display
errors in our code?
The error descriptions are stored in the cErrorsList of the first card
of stack "revErrorDisplay". You could edit those, but you'd need to d
Hi Richmond,
On Wed, Nov 19, 2014 Richmond wrote:
> In an ideal world (which, in case you don't know; this is not)
> an Open Source project should be 100% open; meaning
> we can edit everything . . .
Actually, this not really possible.
Developers who do not understand how
LiveCode works could ma
On 19/11/14 19:52, Alejandro Tejada wrote:
Recently, Richmond wrote:
Fantastic news:
http://livecode.com/blog/2014/11/18/markingdown-the-user-guide/
This blog post describes the work in progress
to include LiveCode User Guide in GitHub.
Now, I wonder if, in the same way,
Could we edit error
Recently, Richmond wrote:
> Fantastic news:
http://livecode.com/blog/2014/11/18/markingdown-the-user-guide/
This blog post describes the work in progress
to include LiveCode User Guide in GitHub.
Now, I wonder if, in the same way,
Could we edit error messages in Livecode IDE
to make them more me
14 matches
Mail list logo
