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
Bug description
When looking at a diff using iceberg's commit window, the horizontal scrollbar has incorrect bounds and does not allow for scrolling, therefore it's impossible to see the changes in long lines.
To Reproduce
Steps to reproduce the behavior:
Go to Iceberg
Click on: a repository where you'd like to do a commit.
Click on commit.
Select a change with a long line
Try to scroll horizontally to see the changes.
Expected behavior
Window should allow looking at all the code in the diff sections.
It seems like RubAbstractTextArea & friends do not offer any kind of "size to fit" method, causing issues like this. Devising a fix is not so easy, but can be done by performing a rudimentary implementation of this functionality:
RubAbstractTextArea>> maxLineWidth [
| w |
w :=0.
self string linesDo: [ :line | w := w max: (self font widthOfString: line) ].
"check this later, not really sure about this calculation"^ w *6//5
]
RubAbstractTextArea>>handleEdit: editBlock [
"Ensure that changed areas get suitably redrawn"
editBlock value.
"Fit to width on edit"
(self grow isNotNil &self grow) ifTrue: [
selfwidth: (1max:self maxLineWidth +self margins left +self margins right)
].
self selectionChanged "Note new selection"
]
This might not be exactly the cleanest solution, but it does resolve the issue for the most part and makes viewing changesets in Iceberg (and Epicea) less tedious.
Bug description
When looking at a diff using iceberg's commit window, the horizontal scrollbar has incorrect bounds and does not allow for scrolling, therefore it's impossible to see the changes in long lines.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Window should allow looking at all the code in the diff sections.
Screenshots
Version information:
Expected development cost
🤷♂️
The text was updated successfully, but these errors were encountered: