Alex Tweedly alex at
Tue Aug 1 16:29:18 EDT 2017

I have to admit, I had the same complaint as Andre - I didn't see 
anything about it in the dictionary.

OK, now that I've looked harder, I see them :-)

But I had no idea there was library documentation within the "API" 

Brings up another question - I see there's a 'getopt' library for 
parsing command line arguments, but I can't find a way to run with 
command line arguments. I thought it was, in my case, 
<pathtoengine>/Livecode-Indy -u

but that simply says "Startup error - cannot run in command line mode"

Is there some other new way to do this ?

-- Alex.

On 01/08/2017 21:18, Monte Goulding via use-livecode wrote:
>> On 2 Aug 2017, at 4:02 am, Andre Garzia via use-livecode <use-livecode at> wrote:
>> I wish there was a more comprehensive documentation effort going on.
> Hi Andre
> Can you give a little more detail on your complaint here. All our new libraries are documented with lcdoc block comments which are extracted during the build and appear in the documentation. At the moment you need to choose the extension you are interested in as they don’t appear in the LiveCode Script api but in the future we will change this so all things available from LiveCode script are in the LiveCode Script API section.
> Cheers
> Monte
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

More information about the Use-livecode mailing list