Reference of Standard Handlers & Properties

[Perry]

Is there a standardized List of Properties and Handlers for each control?

Push Button
Handlers
mouseDown
mouseMove
mouseUp
????
Properties
name (string value)
label (string value)
toolTip (string value)
style (string value)
visible (true/false)
opaque (true/false)
showName (true/false)
etc....
????

Text Entry Field
Handlers
mouseDown
mouseMove
mouseUp
textChange ????
????
Properties
name (string value)
toolTip (string value)
disabled (true/false)
visible (true/false)
opaque (true/false)
etc....
????
(I had this list formatted but that seems to be removed)
This would be a big help if there was such a thing for download. Tutorials are fine and I've learned some from them, but a reference such as this would be a big help.
At this point I'm reduced to guessing.
A lot of false starts and frustrated attempts.

[Klaus]

Hi Perry,

hello and welcome to the forum!

I do not know if a list a you describe is available somewhere, but you can open the dictionary
(Menu: Help, first menuitem) and check the left side, where you will find all available messages
etc. for a specific object.

You may also want to look at these stacks to get the basics of Livecode:
http://www.hyperactivesw.com/revscriptc ... ences.html


Best

Klaus

[dunbarx]

Hi.

Use the "properties" property to find all, er, properties. Note that the result of using this is an array. You may want to:

Code: Select all

on mouseUp
   get the properties of yourControl
   combine it with return
   answer it
end mouseUp

Handlers? These are entirely within the purview of the programmer. There are no prepackaged handlers of any kind. That said, some complex objects like dataGrids have many handlers built-in indeed, as well as behaviors and properties.

Craig Newman

[FourthWorld]

Handlers? These are entirely within the purview of the programmer. There are no prepackaged handlers of any kind. That said, some complex objects like dataGrids have many handlers built-in indeed, as well as behaviors and properties.

I think the OP means the messages that handlers can respond to. As Klaus pointed out, and as I was delighted to learn (thanks Klaus) is that the Dictionary can be filtered by object type to provide a list of all token, including both properties and messages, relevant to that object type. There's also a column for token type, and sorting by the column can quickly produce a convenient list of everything requested.