Current behaviour of RnD is to unpause a paused game on any event (or whatever it's called: key-press, key-release, mouse, joystick and all that stuff). My suggestion is to change that so that the game is unpaused only happens on key/button press and not on the release.
Motivation: pretty often it happens that I pause the game when I'm walking (i.e. holding down the arrow key). Sometimes it's just because I don't release the button before pausing, sometimes it's on purpose - there are levels where timing is very important. Now, if I must do something urgently, I sometimes don't even notice that the game was unpaused almost instantly after I paused it - because I released the arrow button.
Therefore this behaviour is a bit unhandy to me and I'd like to see it changed if it's not a big problem (and since the longstanding bug of treating mouse wheel as a button was fixed recently, I really hope this issue will also be addressed ;-).
Don't unpause on release-key.
Moderators: Flumminator, Zomis
Just checked this -- never really noticed this before.
It really feels "wrong", and should indeed be fixed. Shouldn't be too hard...
> If this will be changed, please add an option that emulates original behavior.
Is this really needed? Does this "malfunction" has any use worth adding such a switch? (Fixing it should not break any level, and I see no reason to keep the old (mis)behaviour available.)
It really feels "wrong", and should indeed be fixed. Shouldn't be too hard...
> If this will be changed, please add an option that emulates original behavior.
Is this really needed? Does this "malfunction" has any use worth adding such a switch? (Fixing it should not break any level, and I see no reason to keep the old (mis)behaviour available.)
Fixed now. (I really think this was to be treated as a bug.)
> I really hope this issue will also be addressed ;-).
Yes, this one was quite nasty (once I noticed it ;-) ).
A new version including this fix will probably be released very soon, as there are quite a number of other bugs that really have to be fixed as soon as possible for the current release version.
> I really hope this issue will also be addressed ;-).
Yes, this one was quite nasty (once I noticed it ;-) ).
A new version including this fix will probably be released very soon, as there are quite a number of other bugs that really have to be fixed as soon as possible for the current release version.