Took up Ali's invitation to give amending the LC Dictionary via GitHub a go.
With regard to - do as
The OS X explanation of 'the result' is quite straight forward and easy to
demonstrate.
On OS X systems any result returned by the script language is placed in the
> result.
do "6 / 2" as
On Wed, Feb 3, 2016 at 10:25 AM, Kay C Lan wrote:
>
> I see in the last script how you've declared in VBScript, but I
> believe this below script is also your script and is not declared,
> you simple check LC's own 'the result'.
>
> (line wraps are probably all over
On Wed, Feb 3, 2016 at 5:08 AM, Kay C Lan wrote:
>
> Searching the List for VBScript examples I see nowhere where a global
> 'result' variable is defined but a simple test if LC's 'the result'
> contains "error".
>
Here is a VBScript I have used in the past that sets
Ah, just the person I was hoping would answer.
I see in the last script how you've declared in VBScript, but I
believe this below script is also your script and is not declared,
you simple check LC's own 'the result'.
(line wraps are probably all over the place)
##
put the
Thanks Mark, that is certainly much clearer than what the Dictionary says.
I've found this nice short example on the List but before I add it to the
Dictionary I would appreciate if someone could confirm it works in the
latest version of Windows. The poster made a snide comment that it may or
may
On 2016-02-03 16:25, Kay C Lan wrote:
So again this leave me wonder as to the real situation with Windows?
Can it
be like OS X where you simply check LC's 'the result' ? On Windows how
do
you know when you NEED to declare in VBScript and when you
don't ?
My AppleScript and VBScript are a