LiveCode Forums

Here's the tl;dr of how I go from debugger to script editor. ymmv. /** * editScriptAt * * pSelection : chunk - "char start to end of line n" * pObject : name of object to be edited */ constant kIDEScriptEditor = "revNewScriptEditor 1" private command editScriptAt pSelection, pObject local tChunk loc...

Not a command, but if you catch the trace or traceBreak messages in a frontscript you get the proper arguments.

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

LOL.
I do want to say, though, that PowerDebug has the option to change the text font and size for both the variables display and the script view.

Should be a simple matter of renaming your current installed version and then reinstalling. Then you'll have something to compare the virgin installation with.

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

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 set the cErrorsList of stack "revErrorReport" to the scriptExecutionErrors set the cScriptErrors of stack "revE...

tetsuo29-

I stopped installing for "all users" a while back to make my life simpler, especially for uninstalling.

Of course, all this could be solved with a proper linux installer, but LC has never had one of those.

Heh. Well, I did say "mostly".

And yes, I also do the construct in cases where <something> is a three-state boolean: true, false, empty.
That resolves it to true or not true.

Look at Richard's message diagram again - background scripts come right before the engine. So everything in it is fair game for any stack or control.
If you want your script to respond only to explicit calls then your best bet would be to make it a substack.

Indeed it is. My writing before thinking.
But mostly I tend not to use negative conditionals anyway, because I find it makes code easier to read.

Whew! Well, I would have preferred it as an attachment, but... a couple of things from a quick overview (I take it --elvis is so you can say "find Elvis") LiveCode doesn't accept the mac "≠" character as an operator, so you'll have to use "!=" or say "is not" or something similar. ...don't get me st...

I think Kevin's response at 13:08 to why xavvi is important is brilliant. Xavvi basically sidesteps the 6-week language and environment learning curve.

Back to your original problem though... If you launch with IDE without your backscript does the message box look ok? If it still has the weird objects then my guess is that your backscript intercepted the save message, possibly by changing the default stack or possibly by making the message box the ...

Ah! The Updates tab. Thanks - that's what I was missing.