New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Commit Dialog: Commit button not as the default button #5644
Comments
This annoying behaviour exists in 2.51.04 |
@mstv I dont think this is a bug because when you open the commit dialog , commit button by default has the focus and on pressing enter, the action triggers. |
Undo default button setting in FormCommit. Reverting changes introduced in * 4449536 * a688346 Closes gitextensions#5644
Yes, sorry, next time I will really check it with 2.5x. (I wonder why it didn't happen to me before, but several times last week.) |
Could you please give it a good run for the money - https://ci.appveyor.com/api/buildjobs/m5jw7hjxqcikl3h5/artifacts/Setup%2FGitExtensions-Portable-3.00.00.4000.zip |
The Commit dialog works as expected. |
Thank you. |
Undo default button setting in FormCommit. Reverting changes introduced in * 4449536 * a688346 Closes gitextensions#5644
Do you want to request a feature or report a bug?
unlucky UX, regression
What is the current behavior?
Hitting the
Enter
/Return
in the Commit Dialog triggers theCommit
button if the un/staged file lists have the keyboard focus.This resulted in several incomplete commits. I do not want to amend commits (at least not for this reason).
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
Enter
/Return
What is the expected behavior?
The
Commit
action shall never be triggered by just hittingEnter
/Return
(unless the regarding button has the focus).It can already be triggered by the existing hotkey
Ctrl
+Enter
/Return
(which should be displayed in the tooltip of theCommit
button).Environment you encounter the issue:
Did this work in previous version of GitExtensions (which)?
2.5, older master
The text was updated successfully, but these errors were encountered: