[gryf73]

> ...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...

[badsectoracula]

> I'm using dual monitor on daily basis and occasionally connect additional one, and didn't get "dual dock" for years.

I think there was a misunderstanding here, i wrote "duplicate the dock configuration", not that there was a "dual dock" on screen. Basically if you open `WMState`, under the `Dock` node you'll see something like `Applications { ... }` but also an `Applications<height> { ... }`.

The reason being that Window Maker uses the current screen height to identify which dock to load/save by attempting to load `Applications<height>` and if there isn't such an entry (it doesn't try other heights), it reverts to `Applications`, if any or just destroys the dock.

This behavior (which has been here since 1999[0]) combined with restarting whenever RandR restarts means you get to lose your dock setups whenever the resolution changes. Or if you want to be more generous, you get to use a different dock per resolution.

Which is why i do not have RandR compiled it.

> Nope [1]. Not for those message types.

Yeah, sorry, i meant _NET_FRAME_EXTENTS for calculating frame size, which causes issues with Wine and some other applications.

[0] https://github.com/window-maker/wmaker/blob/3c046182788196eb... (check the commit at the top)

[gryf73]

> I think there was a misunderstanding here, i wrote "duplicate the dock

Oh, right. For me it will always be messed up dock conf, when resolution of the screen, where dock resides, will be lesser than actual dock height. I guess that thing deserve a bug report. I bet most of users would expect to have dockapps preserved even if those are out of reach because of screen size.

> Yeah, sorry, i meant _NET_FRAME_EXTENTS for calculating frame size,

That's true.

FWIW even with those annoyances, wmaker is still usable. The only things which manifests to me are virtualbox trying to fight wmaker in window placement and steam launcher which lacks of ability to move around with mouse (without modifier key).

TBH, I'm pretty happy with it, perhaps my workflow plays a role here, as I'm rather keyboard person, and mouse is used mostly on web browser.