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
Do you want to request a feature or report a bug?
Reporting a bug
What is the current behavior?
In the commits view, I can't change all column widths correctly.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
Widen the columns "commit message" and "committer"; the field "commit date" will become smaller. Then try to make those fields smaller again; you'll see that the field "commit date" can't be made wider.
What is the expected behavior?
I expect all field widths in the view to be adjustable to both sides.
Environment you encounter the issue:
Windows
GitExtensions version: 2.51.01
GIT version: git version 2.16.2.windows.1
OS version: Windows 10 pro 10.0.16299.371
Did this work in previous version of GitExtensions (which)?
It did work, not sure till which version exactly.
PS thanks Russkie for your comment
The text was updated successfully, but these errors were encountered:
Hi Drew,
thanks for the reply and fix!
Any expectations when the v3 final will be out?
TIA Raymond
2018-06-18 19:23 GMT+02:00 Drew Noakes <notifications@github.com>:
Do you want to request a feature or report a bug?
Reporting a bug
What is the current behavior?
In the commits view, I can't change all column widths correctly.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
Widen the columns "commit message" and "committer"; the field "commit date" will become smaller. Then try to make those fields smaller again; you'll see that the field "commit date" can't be made wider.
What is the expected behavior?
I expect all field widths in the view to be adjustable to both sides.
Environment you encounter the issue:
Windows
Did this work in previous version of GitExtensions (which)?
It did work, not sure till which version exactly.
PS thanks Russkie for your comment
The text was updated successfully, but these errors were encountered: