Skip to content

Slight adjustment to the interface#33

Closed
alshopov wants to merge 1 commit into
j6t:masterfrom
alshopov:pack
Closed

Slight adjustment to the interface#33
alshopov wants to merge 1 commit into
j6t:masterfrom
alshopov:pack

Conversation

@alshopov

Copy link
Copy Markdown
Contributor

Make the the following tk widgets take all available horizontal space within their parent and expand with the application window:

  • .vpane.lower.commarea.buffer
  • .vpane.lower.commarea.buffer.frame
  • .vpane.lower.commarea.buffer.frame.t (via ui_comm variable)

This allows the commit message editor along with its widgets reflow This is visually better on very wide monitors plus it is the same behavior as the widget above

Make the the following tk widgets take all available horizontal space
within their parent and expand with the application window:
- .vpane.lower.commarea.buffer
- .vpane.lower.commarea.buffer.frame
- .vpane.lower.commarea.buffer.frame.t (via ui_comm variable)

This allows the commit message editor along with its widgets reflow
This is visually better on very wide monitors plus it is the same behavior
as the widget above

Signed-off-by: Alexander Shopov <ash@kambanaria.org>
@alshopov

Copy link
Copy Markdown
Contributor Author

Here is demonstration of the intended behavior:

Here is the standard behavior of master

And here is the visualization when you resize the app window with the patch applied

@j6t

j6t commented Jun 15, 2026

Copy link
Copy Markdown
Owner

This change is not desirable in this form. The Options dialog has a setting for the width of the commit message area in characters. This width must be obeyed.

I can imagine that we reserve a special value, say dynamic, that achieves the behavior that you desire.

@j6t

j6t commented Jun 15, 2026

Copy link
Copy Markdown
Owner

Concerning the commit itself, please be more specific in the title and follow the usual style, in particular, the "git-gui:" prefix. In the body, it is not necessary to call out the widget names in the code, but rather tell what they are ("the commit message field and ...").

@alshopov

Copy link
Copy Markdown
Contributor Author

@j6t: thanx for the feedback. I will do one more round of improvements. I will probably bounce the patch off the mailing list once I handle your comments.

@alshopov

Copy link
Copy Markdown
Contributor Author

@j6t I am closing this pull request and opening #34 - I messed up my pushes and Github started acting a bit strange. Sorry for the inconvenience - my bad.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants