Open alembiq opened 1 year ago
The change between those two versions was Razor window used to be locked to fixed since, in 1.8.61.0 I changed it to allow the user to resize it like most windows.
I'm not familiar with i3wm, but sounds like it takes windows that can be resized normally and stretches them instead of giving you the ability to control the size.
Does this issue occur on other apps that also are regular windows? I did confirm using mono, the window size works as expected, though not sure that helps you.
i3wm as tilling manager generally stretches all the windows and tiles to the screen with the same size. You can decide which of the windows goes bigger, and which is smaller, so you can resize it, and I can resize razor in this way.
Before the change happened, it was a floating window (as can could not change the size). Generally, I can make any window floating, but to do that, I need the app to have a property called WM_CLASS
so I can specifically address it.
However, Razor doesn't have this property, so I cannot add a specific rule for it.
The tool I use to get WM_CLASS
is xprop
as showed above.
I'm running ClassicUO 0.1.11.53 (UO Renaissance).
I'm using i3wm as tilling window manager under Manjaro Linux.
Up until recently, I was using razor 1.7.4.49, and everything was great :) Razor was a nice floating window. Since I've updated to 1.8.61.0 razor is not willing to float, and it's behaving as a regular window, being stretched by the i3wm across the whole screen.
Older razors were floating without any configuration, but at this point I'm not able to make it floating again :( Generally, when I want to make a window floating - I need to use xprop on the window and get its "WM_CLASS", and add it i3wm config. For some reason, WM_CLASS isn't part of the xprop output for any of the versions. But there are some differences that might have caused the change in window behaviour.
I can of course do a manual overload on any window, but I didn't needed to in the past :(