I lost my property inspector
Kay C Lan
lan.kc.macmail at gmail.com
Wed Apr 30 22:59:26 CEST 2014
I have seen something very similiar to what you are experiencing and I
believe the cause was the incorrect naming of both Custom Property Sets and
Custom Properties and my use of array notation. This from the User Guide:
Custom Property Names
The name of a custom property must consist of a single word and may contain
any combination of letters, digits, and underscores (_). The first
character must be either a letter or an underscore.
Custom Property Set Names
The names of custom property sets should consist of a single word, with any
combination of letters, digits, and underscores (_). The first character
should be either a letter or an underscore.
It is possible to create a custom property set with a name that has more
than one word, or that otherwise doesn't conform to these guidelines.
However, this is not recommended, because such a custom property set can't
be used with the array notation described below.
THESE NAMING CONVENTIONS DO NOT APPEAR IN THE DICTIONARY, at least not
under the entries for customProperties, customPropertySet,
customPropertySets. And, as if to tempt you into dark and foreboding
corners, the example for customPropertySet is:
set the customPropertySet of me to "Mac Properties"
Do you have Custom Property Sets and/or Names that do not conform to the
above convention? Are you using array notation to refer to them?
On Thu, May 1, 2014 at 12:01 AM, Dar Scott <dsc at swcp.com> wrote:
> I found a workaround.
> It turned out to be just that one button on that one stack.
> I can open the object inspector on some other object and after a few
> seconds it comes up.
> Then I can click on that bad button after that and the object inspector
> comes up with weird values in the fields. “Combobox Menu” in the name
> field and ‘stack revTemplatePalette”’ in the label field and most of the
> controls are dimmed. I try it again and it works.
> So I can get it working, but I think my stack is broken. I have no idea
> how a broken stack can keep the object inspector from working. This is
> just a plain stack.
> So I figure either the stack is corrupted (maybe by a LiveCode bug) or I
> did something to the stack and in particular that button.
> Any ideas on what I could have done?
> On Apr 28, 2014, at 5:27 PM, J. Landman Gay <jacque at hyperactivesw.com>
> > On 4/28/14, 5:54 PM, Dar Scott wrote:
> >> Could something in the preferences do this?
> > That was my first thought, especially since it persists across different
> versions of LC. Trash your prefs.
> > --
> > Jacqueline Landman Gay | jacque at hyperactivesw.com
> > HyperActive Software | http://www.hyperactivesw.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
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the use-livecode