LiveCode Forums.

The online dictionary has the same flaw as every dictionary- you have to know what to look up.

For example, I want to know my options for commenting code. I put "comments" in the dictionary search, and I get no matches.

Really? That is a pretty important and universal need.

It would be great if the dictionary search could return searches based on attributes of the dictionary entry, and not just the language item.

Have you read the User Guide?

Hi,

You are absolutely right and you describe the problem accurately: you need to know what you want to look up. As you must have been thinking already, if you know what you want to look up, then usually you don't need to look it up anymore.

An alternative to the built-in dictionary is Björnke's BvG Docu. It has full-text search, which means that you don't need to know what you're searching for. Just enter something like "field" and you get all entries that involve fields.

If you open the user guide in a PDF reader with search features, you can easily do a full text search on it.

On a side note, although my book is available as a real book only, it comes with a 9 page index, allowing you to find hundreds of subjects for which you can't search in the original dictionary.

Kind regards,

Mark

Hi Mark,

Your book looks great - well done. Don't suppose you're going to make it available as an e-book though are you ?
All manuals like this one looks to be are a fantastic knowledge base to all users up to and above intermediate. I generally find that it's best to source (and have available on my desk) at least 2 or 3 of them if possible - generally what's 'missing' in one can be found in another and all-in-all one can save hours just having them available !

KirbyGlad is right - I had precisely the same issue ! And continue to have it with respect to the properties associated with a particular control... never mind...

Regards.

If you go through the Preferences option when you set up Livecode

Edit/Preferences and go to 'Script Editor' (fifth from the top) down the bottom

there's an option 'Comment using' and you can choose between -- , # and //

so no documentation needed on that one at least.