Error info about try/catch

[jacque]

I'm not sure why it's omitted in standalones, so I'm confused too. Especially since the error codes are duplicated in the revErrorDisplay stack. I haven't looked but it's possible that scriptExecutionErrors contains IDE errors that wouldn't apply to standalones.

[mwieder]

If you include the revErrorReport stack in your standalone then you do have access to the list, but you have to grab it yourself.
In the script for revSaveAsStandalone.livecodescript I see

Code: Select all

      set the cErrorsList of stack "revErrorReport" to the scriptExecutionErrors
      set the cScriptErrors of stack "revErrorReport" to the scriptParsingErrors

so in your standalone app you could

Code: Select all

get line pErrorNum of the cErrorsList of stack "revErrorDisplay" 

Edited... Nope. That doesn't work. Standalone apps are explicitly banned from displaying error strings.
In mode_standalone.cpp I find

Code: Select all

// We don't include error string in this mode
const char *MCparsingerrors = "";
const char *MCexecutionerrors = "";

So the only way I've found to have the error strings in a standalone app is to set a custom property and then use that:
From the message box before building the standalone:

Code: Select all

set the uScriptExecutionErrors of stack <mainstack> to the scriptExecutionErrors

and then in the standalone's error handling code

Code: Select all

get line pErrorNum of the uScriptExecutionErrors of this stack

[FourthWorld]

Remember when IDE-specific handlers had a prefix which allowed is to identify them as such?

This confusion about error string availability is another example of why that was useful.

[mwieder]

Maybe. But it's not a handler, it's a system property.

[FourthWorld]

Maybe. But it's not a handler, it's a system property.

All the weirder, a system property unavailable to standalones built with the system.

[mwieder]

Bug report is here
https://quality.livecode.com/show_bug.cgi?id=20250

[stam]

Sadly looks like it was hibernated 6 years ago…