forked from prusa3d/PrusaSlicer
-
-
Notifications
You must be signed in to change notification settings - Fork 525
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
Infill Sparse Percentage box is not wide enough. Can't see the number #1573
Labels
fix is live in the last release
Please download /build the last release and try to reproduce.
problem
Comments
Also, no I do not have any scaling set. |
That's weird. The boxes are shorter than expected. |
supermerill
added
fixed for the next version
That means that you should be able to test it in the latest nightly build
and removed
awaiting response
Further information is requested
labels
Sep 26, 2021
That is the only one with problems that I can find. |
supermerill
added a commit
that referenced
this issue
Sep 26, 2021
…e left instead of the right Better spacing for infill lines, allowing larger infill % field fix #1573
supermerill
added
fix is live in the last release
Please download /build the last release and try to reproduce.
and removed
fixed for the next version
That means that you should be able to test it in the latest nightly build
labels
Oct 8, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
fix is live in the last release
Please download /build the last release and try to reproduce.
problem
Describe the bug
The location where you set the infill percentage is not wide enough to see or edit the number.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The box to be wide enough to view and edit a value as high as 100
Screenshots
Desktop (please complete the following information):
Additional context
I am not certain if this is a linux specific issue but all other GUI elements seem to be correct.
The text was updated successfully, but these errors were encountered: