Re: Is 'Error Lookup' broken?

It showed up light blue in a script, but when I right-clicked it and selected Find In Docs nothing happened. Then a rift opened in the space time continuum, and there was James Tiberius Kirk Bob S On Oct 14, 2016, at 09:23 , Devin Asay >

Re: Is 'Error Lookup' broken?

Runs slower, but is much more fun: Type response Think twice Think thrice Go have a beer Go have another beer Go have a few more Stop thinking altogether Open computer in the morning and think, "What was I thinking?" Correct response Hit send Bob S

Re: Is 'Error Lookup' broken?

Ohhh... handy tip of the week! Bob S > On Oct 13, 2016, at 08:07 , Mark Wieder wrote: > > On 10/13/2016 07:30 AM, Graham Samuel wrote: >> I should have asked as a supplementary how one might find the textual >> version of numerical error codes oneself, for example, I

Re: Is 'Error Lookup' broken?

> On 15 Oct 2016, at 8:15 AM, Richard Gaskin wrote: > > Dude, don't get me started on "Why is this IDE thing this way?" ;) We accept pull requests and bribes ;-) Cheers Monte ___ use-livecode mailing list

Re: Is 'Error Lookup' broken?

/Is-Error-Lookup-broken-tp4709348p4709408.html Sent from the Revolution - User mailing list archive at Nabble.com. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription

Re: Is 'Error Lookup' broken?

Monte Goulding wrote: > I suspect what Ali found odd was setting a custom property at startup > from an engine property didn’t make sense. I find it odd too. Better > to use the engine property directly where needed. Dude, don't get me started on "Why is this IDE thing this way?" ;) I have a

Re: Is 'Error Lookup' broken?

> On 15 Oct 2016, at 7:55 AM, Richard Gaskin wrote: > > Prior to the error descriptions being added to the engine they had to be > somewhere, and since the error dialog was the one place they were always > needed putting them into a custom prop there made

Re: Is 'Error Lookup' broken?

Ali Lloyd wrote: > It's not actually correct that they were introduced in LC8 -- > the properties have been there since at least 6.0.1 ( > https://github.com/livecode/livecode/blob/release-6.0.1/engine/src/lextable.cpp#L1343) > and probably before. > > Previously the home stack would set the

Re: Is 'Error Lookup' broken?

It's not actually correct that they were introduced in LC8 -- the properties have been there since at least 6.0.1 ( https://github.com/livecode/livecode/blob/release-6.0.1/engine/src/lextable.cpp#L1343) and probably before. Previously the home stack would set the custom property of the error

Re: Is 'Error Lookup' broken?

> On Oct 14, 2016, at 1:24 PM, mwieder wrote: > > Devin- > > Both the scriptExecutionErrors and scriptParsingErrors global properties are > currently undocumented. These contain the same lists that were formerly > custom properties of card 1 of the error display stack.

Re: Is 'Error Lookup' broken?

Wieder ahsoftw...@gmail.com - -- Mark Wieder ahsoftw...@gmail.com -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Is-Error-Lookup-broken-tp4709348p4709396.html Sent from the Revolution - User mailing list archive at Nabble.com

Re: Is 'Error Lookup' broken?

The fact that scriptExecutionErrors function is undocumented is a confirmed bug. I’m not very familiar with it, but if anyone would supply me with a simple description I would be happy to add it to the Dictionary on github. Devin > On Oct 13, 2016, at 10:51 AM, Graham Samuel

Re: Is 'Error Lookup' broken?

Thanks Richard - I didn’t know how to update a plugin but I worked it out (you have to delete the old one manually). Anyway very useful - thanks to you and to Jacque. Graham > On 13 Oct 2016, at 18:01, Richard Gaskin wrote: > > I was mistaken: it seems Jacque has

Re: Is 'Error Lookup' broken?

: http://runtime-revolution.278305.n4.nabble.com/Is-Error-Lookup-broken-tp4709348p4709359.html Sent from the Revolution - User mailing list archive at Nabble.com. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe

Re: Is 'Error Lookup' broken?

I uploaded a revision to User Samples some time ago when the problem first arose. It branches lookups based on the LC version. Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On October 13, 2016 10:35:19 AM

Re: Is 'Error Lookup' broken?

I was mistaken: it seems Jacque has already updated the tool to use the scriptExecutionErrors function (apparently undocumented) if the older error string list stored in stack "revErrorDisplay" is empty. This should allow it to work in all versions from at least 5.5 and later. Perhaps you

Re: Is 'Error Lookup' broken?

Phew - that at least is a simple fix! Thanks - G > On 13 Oct 2016, at 17:38, Ali Lloyd wrote: > > It's 'scriptExecutionErrors' > > On Thu, Oct 13, 2016 at 4:22 PM stephen barncard < > stephenrevoluti...@barncard.com> wrote: > >> On Thu, Oct 13, 2016 at 8:17 AM, Graham

Re: Is 'Error Lookup' broken?

It's 'scriptExecutionErrors' On Thu, Oct 13, 2016 at 4:22 PM stephen barncard < stephenrevoluti...@barncard.com> wrote: > On Thu, Oct 13, 2016 at 8:17 AM, Graham Samuel wrote: > > > put the number of lines of the executionerrors > > > double-take :this looks like

Re: Is 'Error Lookup' broken?

Graham Samuel wrote: > I love the ‘LiveCode Error Lookup” plugin (by Richard Gaskin, revised > by Jacque Gay), but in 8.1.1 (rc2) it doesn’t seem to work - am I > doing something stupid? My hunch is that the location of the error strings has changed between versions. I'll have to let Jacque

Re: Is 'Error Lookup' broken?

On Thu, Oct 13, 2016 at 8:17 AM, Graham Samuel wrote: > put the number of lines of the executionerrors double-take :this looks like executioners when glanced at quickly. Yikes. First 'Delete Stack', now this! ... gotta turn the news off... Stephen Barncard -

Re: Is 'Error Lookup' broken?

Spoke too soon - doesn’t work for me on 8.1.1 rc2. Also put the number of lines of the executionerrors just gives ‘bad factor’. Confused… ] > On 13 Oct 2016, at 17:09, I wrote: > > Thanks very much Mark. G > >> On 13 Oct 2016, at 17:07, Mark Wieder wrote: >> >> put

Re: Is 'Error Lookup' broken?

Thanks very much Mark. G > On 13 Oct 2016, at 17:07, Mark Wieder wrote: > > put line 347 of the executionerrors ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and

Re: Is 'Error Lookup' broken?

On 10/13/2016 07:30 AM, Graham Samuel wrote: I should have asked as a supplementary how one might find the textual version of numerical error codes oneself, for example, I have an error 347,0,0 put line 347 of the executionerrors -- Mark Wieder ahsoftw...@gmail.com

Re: Is 'Error Lookup' broken?

I should have asked as a supplementary how one might find the textual version of numerical error codes oneself, for example, I have an error 347,0,0 and later 76,549,1 253,549,1 These are all to do with trying to delete a stack which has already been closed, like the IDE does with ‘close

Is 'Error Lookup' broken?

I love the ‘LiveCode Error Lookup” plugin (by Richard Gaskin, revised by Jacque Gay), but in 8.1.1 (rc2) it doesn’t seem to work - am I doing something stupid? Graham ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to