irog at mac.com
Thu Jan 13 13:56:42 EST 2011
On Jan 13, 2011, at 11:00 AM, use-livecode-request at lists.runrev.com wrote:
> Message: 12
> Date: Thu, 13 Jan 2011 08:56:44 -0700
> From: Devin Asay <devin_asay at byu.edu>
> To: How to use LiveCode <use-livecode at lists.runrev.com>
> Subject: Re: Vent!
> Message-ID: <FC232843-0F30-4728-BA86-04433F36DA58 at byu.edu>
> Content-Type: text/plain; charset="us-ascii"
> On Jan 12, 2011, at 9:57 PM, Jeff Massung wrote:
>> I know it's a vent/rant, and while LC is completely awesome in -many- I have
>> to completely agree with this... I don't know how many times I've been
>> bitten switching to the pointer tool and think I'm typing something in a
>> field only to change the name of the stack w/o realizing it and cause myself
>> 15+ minutes worth of problems.
>> I'm not sure closing the inspector makes sense, but certainly making it so I
>> can't accidentally screw myself in pointer mode would be nice. ;-)
>> Jeff M.
>> On Wed, Jan 12, 2011 at 8:13 PM, Roger Guay <irog at mac.com> wrote:
>>> Hi Folks,
>>> The most annoying thing I experience with LiveCode is when stack properties
>>> get inadvertently changed after switching from the Pointer tool to the
>>> Browse tool and vice versa, whilst the Property Inspector is open. Can
>>> anyone suggest a way around this without locking or manually closing the
>>> inspector? I would prefer that the inspector automatically close when
>>> selecting the Browse tool instead of it reverting to the stack properties.
>>> Better yet, I would prefer it to not change and remain focussed on the last
>>> control! TIA.
> I agree, it's a problem, especially for new users. But even after 10 years it still rears up and bites me in the backside every once in a while. The results are never pretty. Still, it's a big improvement over early versions of Rev where it seemed I was always renaming stacks and wreaking havoc on my projects.
> A thought just occurred to me--what if you opened the property inspector for the stack and locked it? Then you could open a second, unlocked property inspector that would be live for other objects, but would not flip to the stack when you went into run mode. I haven't tested it, but it seems like that would at least reduce the likelihood of inadvertently changing stack properties.
> Devin Asay
> Humanities Technology and Research Support Center
> Brigham Young University
Good thought, Devin. Unfortunately it doesn't work. The inadvertent name change is still made to the stake, and the Inspector reads "Another inspector is operating on this object". BTW, I have determined that this problem always occurs if I use the CommandKey+9 keys to go to the Browse tool when the Pointer tool is over the Inspector. Do you think I could train myself to not do that? Not gonna happen!!
Thanks and cheers,
More information about the Use-livecode