I lost my property inspector
dsc at swcp.com
Thu May 1 18:07:34 EDT 2014
I got this when dropping an Option Menu on 7.0dp3 . I took a picture of it. This didn’t have the way-off-screen or wrong mode like I saw before. Do you have a bug report I can upload the picture to?
On Apr 30, 2014, at 9:01 PM, Bob Sneidar <bobsneidar at iotecdigital.com> wrote:
> Dar, your stack is not broken. I reported this last week, and only a few people could reproduce it. I got the same results with a new stack. I suspect that people were not following my recipe, and so did not see the problem. Try this:
> 1. Quit Livecode
> 2. Launch Livecode
> 3. Create new stack
> 4. Drag combo box into new stack
> 5. Get properties of combo box
> You *should* get the same results.
> Your clients are seeing the problem I reported earlier, only I am not sure they know how they produced it. The reason only a few people are see in it, is because if you get ANY OTHER PROPERTIES first, the problem does not exhibit itself. At least this is what my tests revealed. That is why you MUST follow the above formula to see it.
> It may also be that other things will produce this, but I only know of this one. Once you successfully get the properties of an object, you will not see this problem until the next time you start Livecode.
> On Apr 30, 2014, at 06:01 , 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> wrote:
>>> 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:
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> 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