LC 8 Property Inspector

[Peter Haworth]

I've filed several bug reports over the last couple of years regarding
missing properties, mostly related to propertynames and glad to say they
have all been fixed so things are a lot better now than they used to be.
The propertynames still includes things that don't seem like properties to
me, "abbrev" and "working" for example, but no doubt there's a good reason
for that

Regarding your question on which properties are missing that a developer
needs, the answer for me is all the ones that are no longer returned by the
properties of an object and here's why.

As I've mentioned in other emails on this thread, lcStackbrowser gives
users the flexibility to organize properties into groups.  I do this by
displaying a list of all the properties for a particular object type, from
which users can drag and drop their chosen properties into a group list.  I
get that list from the keys of the properties array for the template for
whatever type of object I'm dealing with, but with this change, the list
was suddenly incomplete.

As an example, the height and width properties are no longer included.
Their values can be derived from the rectangle property which is fine if
you want to recreate an object or use their values for some other reason
but I need their names, not their values.

I ended up writing a handler that goes through the propertynames list and
tries to set each one into each of the object templates to determine which
object types it applies to, a time consuming process that really shouldn't
be necessary.

That's all water under the bridge now but I still don't understand why the
contents of the properties property were changed.

Pete
lcSQL Software <http://www.lcsql.com>
Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and
SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html>

On Fri, Oct 9, 2015 at 8:46 AM, Richard Gaskin <ambassador at fourthworld.com>
wrote:

> Peter Haworth wrote:
> > Would be great if you get flexible groupings going.  Having been
> > through implementing this, one thing to watch out for is that there
> > isn't a way to get a complete list of properties for a particular
> > object type.
>
> I know some synonyms are missing, but the properties function was added to
> allow rapid reproduction of an object, so while it may not substitute for
> the Dictionary it should be at least functional for most practical
> development uses.
>
> What properties does a developer need that aren't included?
>
> Let's bug report those and get it behind us.
>
> --
>  Richard Gaskin
>  Fourth World Systems
>  Software Design and Development for the Desktop, Mobile, and the Web
>  ____________________________________________________________________
>  Ambassador at FourthWorld.com                http://www.FourthWorld.com
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>