Mark Wieder wrote:
> I've never liked the idea of hiding things from users.
> Ideally you might want to show groups of properties contextually, but
> the idea that there are properties that exist but you can't get to
> them just does.not.seem.right.
Depends in the purpose.
The properties function was designed to allow one-step transformations
Without it, the old-school way is "set the <label> of something to
<value>" over and over for every property value being changed.
It was not designed for learning or documentation. It was designed
solely for rapid development.
Hence things like htmlText being there but rtfText not. The former is a
tagged textual representation of everything a field can have, while
rtfText is merely a subset of field elements suitable for certain types
If an enhancement request is filed I'd prefer it be for an optional
modifier to the existing function syntax, rather than littering the
current function results with synonyms or subset-value props that aren't
needed for automating property assignment.
Maybe "the full properties of..."?
For the intended purpose, I've been quite happy with "the properties" as-is.
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
use-livecode mailing list
Please visit this url to subscribe, unsubscribe and manage your subscription