OK, I can live with adding those to my list of properties manually for now. Hopefully, the movement to improve "the propertynames" will gather steam so it won;t be necessary to use the properties t get a list of property names for an object.
Pete lcSQL Software <http://www.lcsql.com> On Thu, Jun 13, 2013 at 5:08 PM, Monte Goulding <mo...@sweattechnologies.com > wrote: > > On 14/06/2013, at 9:37 AM, Peter Haworth wrote: > > > Thanks Monte. That code also shows me the various synonyms for the color > > properties. > > > > I don't understand the code well enough to figure this out so I have to > ask > > if this change will now return the unicode variants if they are not set? > > Remember, it's the names I'm interested in, not the values. > > No it won't. The unicode variants are a special case were it's only > possible to return one or the other as far as I can see... luckily it's > only 3 (unicodeLabel/Title,unicodeToolTip,unicodeText of button) > unicodeText of field is covered by the htmlText property. I wanted to only > return the unicode variants for consistency but Mark felt that the ascii > variants should be returned if possible... The issue is it's not an > either/or thing with the unicode variants... both would have a value if one > does... > > -- > M E R Goulding > Software development services > Bespoke application development for vertical markets > > mergExt - There's an external for that! > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode