suddenly deleted text

Hi Alex

I just wanted to check about the functionality of the keystrokes "shift+delete" while when you are editing the multi-choice of true and false fields of a question. To me it seems like you have some function here (whether intended or not?) that will delete or clear the entire field with that keystroke. You do not have to have the text highlighted, and sometimes (I haven’t been able to replicate it on demand) it seems to even delete the previous field too. When any of these sudden deletions occur I always try pressing "CNTRL+Z" but it does not undo the action.

Now you may ask yourself why is he pressing "shift+delete" and beleive me I am aksing myself the same question...... I think the only explanation I have is that it is unintentional slip of the keys. I am often editing my questions and hitting the Home and End keys plus the CNTRL+Arrows left and right to jump and skip through the text. these array of keys are adjacent the Shift and Delete keys so perhaps that is how????

Whether that is a bug or not I guess is something for you to investigate further. But what I would suggest, as another Enhancement request that would potentially reverse this bug should it accidentally occur again, is to have the ability to close down the question properties window without saving changes. I tried clicking on the 'X' in the top right corner hoping that this would ignore the changes just made but no unfortunately I had to close down my quiz without saving the last 5 changes I had intended to make and then start again.

Thank you Adam

I shall see if I can replicate the effect.... and also thank you for your suggestion which I will add to the feature request list.

Thanks Adam, there's definitely something weird going on there with Shift+Delete. I've looked into on other application, and it seems it is most often used as an alternative to 'Cut' (CTRL+C) - and this is how it works in QW when something is selected - but when nothing is selected, it is deleting the whole answer. That's a bug, there'll be a fix in the upcoming 3.5.