bug
Jon
jbondy at sover.net
Sat Jun 4 13:41:13 EDT 2005
A good tip. Better might be an option to disable the <del> key entirely
in this situation, if the developer so desired. Old habits (that work
in every other program on my computer) die hard.
:)
Jon
Stephen Barncard wrote:
> When editing properties, I'd suggest never using the delete key at
> all. Use the trash can icons instead.
>
> Important: use the UPPER trash can to delete single properties, use
> the LOWER trash can to delete property sets. The Delete key is just
> too vague sometimes with multiple hilites all over the place.
>
> At 1:00 PM -0400 6/4/05, Dennis Brown wrote:
>
>> I hate to break in here, but just 10 minutes ago, I wanted to delete
>> a custom property from a field. I selected the property in the
>> inspector (it was the first one and it was highlighted), I hit
>> delete, return (did not read the "are you sure" box very carefully)
>> and every custom property was deleted. I went immediately to the
>> Edit menu and the undo was available, so I selected it. None of my
>> custom properties were restored, but the field was still there. I
>> had to revert to last saved. When I actually try to delete more than
>> one custom property at a time, I can't even select more than one.
>>
>> Perhaps I did something wrong (operator error), but I can not figure
>> out what it could have been. I have noticed that the IDE has a tough
>> time doing the focus right. For instance, I can select the doc
>> window, click in the find field --it is outlined, then start typing,
>> only to look up and see that nothing is being typed into the field.
>> I have to click on it again before it works. This has happened also
>> in my stacks. What gives?
>>
>> Dennis
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>
>
More information about the use-livecode
mailing list