Brad Allen wrote:
> Yes, but those only list the custom properties. Wouldn't it be great
> if you could have a complete list of all properties, commands, and
> functions applicable to a given object? For instance, stacks have
> some properties than fields don't have, and vice versa.
>
> For example,
>
> propertyNames(Revolution) would output a list of global properties,
> such as the textArrows, the stacksInUse, the textArrows, etc.
>
> propertyNames (stack "Whatever") would output a list of properties
> such as the cantDelete, the cantAbort, the name, and whatever custom
> properties are present.
You can get most but not all of the properties of an object using the
properties array, e.g
put the properties of this stack into tProperties
put keys(tProperties)
> functionNames(stack "Whatever") would output a list of functions
> present in the stack script.
You could write a function that would do this by checking through the script
of the stack.
Cheers,
Michael
--
Michael Fisher <[EMAIL PROTECTED]> <http://www.runrev.com/>
Runtime Revolution Ltd - Power to the Developer!
Tel: +44 (0)870 747 1165 Fax: +44 (0)1639 830 707
_______________________________________________
improve-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/improve-revolution
