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
It took me a bit to hunt down exactly the circumstances of this bug, but what buttonSize is set to at first render seems to be a "max" for button-size changes without clipping after that.
Due to this, it's possible to increase button-size from 14 by setting it in your rcfile (which is executed before first render), but any increases at runtime cause the image to be clipped on the right side.
ex:
(with button-size set to 20 in rcfile)
(after wormc button-size 22 is run)
The text was updated successfully, but these errors were encountered:
This can actually be fixed by triggering a re-render by moving the window around or resizing it. The issue is I think the image is re-rendered without the window being resized in the section of the ClientMessage handler which sets button-size. I'll try to fix tomorrow.
It took me a bit to hunt down exactly the circumstances of this bug, but what
buttonSize
is set to at first render seems to be a "max" for button-size changes without clipping after that.Due to this, it's possible to increase button-size from 14 by setting it in your rcfile (which is executed before first render), but any increases at runtime cause the image to be clipped on the right side.
ex:
(with button-size set to 20 in rcfile)
(after
wormc button-size 22
is run)The text was updated successfully, but these errors were encountered: