monte at sweattechnologies.com
Tue Dec 17 00:44:35 EST 2013
On 17/12/2013, at 4:25 PM, Peter Haworth wrote:
> No the original question was how to get a list of the Livecode global
> properties. Mark's code happened to find one that was a stack property
> rather than a global one.
Right but the bug report and pull request was about the stack properties which is what I commented on. All I was saying is it doesn't really matter if we include acceleratedRendering (if RunRev want to) as long as any other properties that aren't saved with a stack are also included so we can follow rules about what's in and what isn't... no synonyms, no read only props, no duplication (text, htmlText, styledText) etc. At least then we know what to expect and what not to expect. Hopefully the refactored engine might have better ways to inspect the properties of an object. I suspect the modularity that will be required for pluggable widgets etc will need it at an engine level anyway. At the moment the properties property is just a list for each object. It doesn't even take advantage of the class hierarchy so common properties are defined only in one list...
M E R Goulding
Software development services
Bespoke application development for vertical markets
mergExt - There's an external for that!
More information about the Use-livecode