top | item 44644527

(no title)

gryf73 | 7 months ago

I'm still using wmaker starting from late 90s (also had couple minor contributions)

> 1. There is practically no RandR support.

It is awkwardly implemented yes, as internally wmaker will restart, although changing resolution works for me most of the time. Wmaker doesn't identify monitors, it talk with xlib to get the layout when new display is detected or removed.

As for double dock - never have double dock issue. Sometimes I ended up with lossing it's configuration, especially in a cases when resolution set for the display is too low. That might happen when no display is detected/connected, then resolution is set to 64x64 pixels by X.

> 2. While there is EWMH support, […]

It's partially implemented, and indeed it lacks of handling self-managed application. Some apps are working fine (AFAIRC GTK3 based) and some don't (steam client), but in general for those which are not cooperate modifier key can be used to move such window around and keyboard shortcuts (which I'm mostly using anyway) to resize. Or to force window to use wmaker decorations as you mentioned.

This issue I've tried to solve couple of years ago[1], found culprit, but I've failed to do so. I've also spend a large chunk of time to compare it with PekWM, where those things are working as intended, but stuck on event handling.

As for composition. You might consider to use standalone one (xcompmgr, compton, picom, etc) just to get the effects.

[1] https://github.com/window-maker/wmaker/issues/20

discuss

order

badsectoracula|7 months ago

> Wmaker doesn't identify monitors, it talk with xlib to get the layout when new display is detected or removed.

It'll restart if anything changes, but the problem is...

> As for double dock - never have double dock issue. Sometimes I ended up with lossing it's configuration, especially in a cases when resolution set for the display is too low.

...that it attempts to create different dock configurations based on the monitor height (you can see that if you check the configuration file). This is something that would make some sense in a pre-Xinerama world where Window Maker would be launched for each monitor, but it doesn't make some sense post 2000s and is really just some ancient hack that nobody bothered to fix.

> It's partially implemented, and indeed it lacks of handling self-managed application.

AFAICT the support is there, but some applications seem to assume some additional de-facto behavior that Window Maker does not have. Initially i also assumed the support wasn't there and i went into implementing it myself, only to find out that it is already implemented - and seemingly works as the spec describes.

gryf73|7 months ago

> ...that it attempts to create different dock configurations based on the monitor

it will create dock based on the new display IF the new display is the primary one. You can have displays in different resolution, and it will work. I'm using dual monitor on daily basis and occasionally connect additional one, and didn't get "dual dock" for years. Let me stress it again - dock conf will get messed up, if resolution for the display is smaller then current dock height.

> AFAICT the support is there

Nope [1]. Not for those message types.

[1] https://github.com/window-maker/wmaker/blob/da676c9e9eff0e40...