Is Shift-Backspace not Bugged?!

[Gage]

Hello all,

For a long time I have found nothing but frustration with the Shift-Backspace key combination deleting objects.

Typically, the only time I key this in is when I am typing an object name in the Property Inspector and make a typo. Maybe also sometimes when I am scripting, but I can't remember the use case exactly. Imagine my surprise when the object I've been working on, often for a decent amount of time, is deleted and unretrievable (since I have not found a way to "Undo Delete Object" somehow.

Is this not a bug? Is there a setting I can change to prevent this deletion? It only ever happens unintentionally, and is therefore only a burden, and never a "feature" for me. Booby traps!

Frustrating, but wondering if anyone has addressed this before or if anyone has a solution. I'll submit a bug report if need be.

Thanks,
Phil E.

[dunbarx]

Hi.

When do you use shift-backspace? What does that do that backspace alone does not?

Craig Newman

[Gage]

Craig,

Absolutely nothing, and in fact, it deletes my object from the stack instead of the last character of whichever field I'm typing in. I meant to express that Shift-Backspace is not an intentional keystroke. I may be typing something like "My Field Name", and when I mistype a char near one of the capital letters, (here 'M', 'F', or 'N'), my pinky does not always come fully off the Shift key while I am pressing Backspace.

It's complicated to explain in words perhaps, but just notice how fast your fingers move as you type... the concept is very similar to biting one's cheek while chewing. My point is that simple miscoordination in typing (which occurs frequently enough to warrant my writing this post) causes the Shift-Backspace combination to be entered, which unfortunately has the unexpected, irreversible, and potentially detrimental effect of deleting my object, even when the LiveCode's focus is in the Property Inspector or the Script Editor.

I have never had any need to intentionally do this, it only happens unintentionally. Thus I am left wondering if it is a bug, if there's a way to turn it off, or if there's a compelling reason to leave lit matches and a tank of gasoline next to the baby's crib, so to speak.

Hopefully my intention is a bit more clear now haha! Thanks for getting back to me.

Best,
Phil E.

[FourthWorld]

I'm unable to reproduce that. Does it happen consistently for you?

I believe a bug related to objects having focus when selected text appears to have focus was identified recently and the fix is in progress: http://quality.runrev.com/show_bug.cgi?id=16159

If you find a repeatable recipe for that please add it to the bug report so they have more data to work with.

[jacque]

This came up on the mailing list and it's a bug that has hit a lot of people. The shift key isn't particularly related, it's a more general issue affecting the currently focused object. I've seen the same problem with whole stacks that visually appear to have focus but do not respond when you click on them.

Hopefully the bug will be fixed soon. If you have a recipe by all means add it to the report. In the meantime, save the stack after every significant change. (I've worn the paint off my "S" key.)