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
Because I am a visually impaired software developer, i work with specific display settings:
200% scale factor
3840x1600
So in effect vertically I have only 800px available.
This works fine in general with fork, but I cannot access the merge button when solving conflicts:
The screen shot is taken from your documentation. On my screen the merge button (1) is completely obscured by the commt message dialog (2) and I couldn't find a way to access the functionality anywhere else.
I would be very happy if you could fix this - rather specific - issue, cause it seems a small thing to change (e.g. just add auto scrollbars to the panel containing the merge button and would help me a lot in my daily work.
I would also be fine with a keyboard shortcut or any other solution as long as the merge function becomes accessible.
Thanks a lot,
Eike Falk
The text was updated successfully, but these errors were encountered:
I am using this version of fork on Windows 11:
Because I am a visually impaired software developer, i work with specific display settings:
So in effect vertically I have only 800px available.
This works fine in general with fork, but I cannot access the merge button when solving conflicts:
The screen shot is taken from your documentation. On my screen the merge button (1) is completely obscured by the commt message dialog (2) and I couldn't find a way to access the functionality anywhere else.
I would be very happy if you could fix this - rather specific - issue, cause it seems a small thing to change (e.g. just add auto scrollbars to the panel containing the merge button and would help me a lot in my daily work.
I would also be fine with a keyboard shortcut or any other solution as long as the merge function becomes accessible.
Thanks a lot,
Eike Falk
The text was updated successfully, but these errors were encountered: