That issue is 4 years old, and I think we closed because it no longer happens on windows (or at least we don’t encounter it in a reproducible way).
One thing to consider, in some windows applications (and I think Slicer is one of them), if you modified the scaling, you will need to log out of windows and and log back in for things to scale correctly in the application.
Yes, I bring it up again because I am actively experiencing it now.
Here is a short video showing the issue at 150% Windows scaling
Here it is again with Slicer relaunched and Windows at 100% scaling
You can see that it goes away completely. I could not find a more recent thread with the issue. I didn’t modify the scaling just for the Slicer app; I could do that. But switching between 150% and 100% Windows scaling replicates this issue for me so far, 100% of the time.
Sorry, James, I had to step out for a minute and forgot to test this.
I set scaling to 100% and 150% on two separate runs. So the order of operations was change scaling → sign out → sign in → open and test Slicer, and then repeat for the other option.
Both options, 100% and 150%, acted exactly as shown in the above videos.