Caused by #88 fix, now that there is always a menuBar, whose width is equal to the icon, the calculation for the xOffset should no longer take this width into account, as the intention is to render the icon and the menuBar on top of each other.
Possibly better fix is to take the largest of these two widths instead of the sum.
I'm preparing to officially fork and make a pull request with a fix but want to register the issue already.
Note that the same behaviour is not observed when talking about normal frames.
Caused by #88 fix, now that there is always a menuBar, whose width is equal to the icon, the calculation for the xOffset should no longer take this width into account, as the intention is to render the icon and the menuBar on top of each other. Possibly better fix is to take the largest of these two widths instead of the sum.
I'm preparing to officially fork and make a pull request with a fix but want to register the issue already.
Note that the same behaviour is not observed when talking about normal frames.