You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: BennieD [Submitted to the original trac issue database at 11.51am, Saturday, 15th January 2011]
Some confirmation of the C shortcut, like "Closing changeset" or similar would be helpful.
I've been hitting C...C...C...C... because I'm used to it from Potlatch 1, and thought it is not a shortcut in 2, because nothing happens.
After seeing the shortcut list, I tried again, and although there is no feedback, sure enough on the next save, it is obviously a new changeset.
The silent closing of the changeset is frustrating, as I now never know what happened.
With wireless keyboard, or even just rappid typing, I need to know that the correct keystroke was received by the program.
Thanks
BennieD
The text was updated successfully, but these errors were encountered:
Author: Richard [Added to the original trac issue at 5.11pm, Sunday, 16th January 2011]
Well, you see, the thing is that we didn't actually have a way to give feedback non-intrusively (a modal dialogue would be inappropriate for this). It's now fixed as of r25065 and r25069.
Reporter: BennieD
[Submitted to the original trac issue database at 11.51am, Saturday, 15th January 2011]
Some confirmation of the C shortcut, like "Closing changeset" or similar would be helpful.
I've been hitting C...C...C...C... because I'm used to it from Potlatch 1, and thought it is not a shortcut in 2, because nothing happens.
After seeing the shortcut list, I tried again, and although there is no feedback, sure enough on the next save, it is obviously a new changeset.
The silent closing of the changeset is frustrating, as I now never know what happened.
With wireless keyboard, or even just rappid typing, I need to know that the correct keystroke was received by the program.
Thanks
BennieD
The text was updated successfully, but these errors were encountered: