Discussion:
FVWM: Per-monitor tags/groups
elliot s
2016-05-24 17:52:45 UTC
Permalink
I did dual-monitor by creating a backing desk per second monitor page.
Monitor 2 paging was done by moving windows between backing and current desks.
I also used temp sticky for monitor 2 windows during monitor 1 paging.
I used fvwmbuttons on monitor 2 for my monitor 2 pager and it had its
own "taskbar".
I'd also changed c code to be able to ChangeButton colorsets for the "pager".
A window which spanned monitors 1 and 2 was defined as a monitor 1 window.
Moving windows between monitors was accounted for.
Ive used this for vnc (double width server screen size) and xrandr.
A bunch of ugly fvwmrc code.

I'll have to give your code a spin.
It looks like your code is doing ChangeButton colorsets also.
Is that a post 2.6.6 change?
Thomas Adam
2016-05-24 18:22:10 UTC
Permalink
Post by elliot s
I did dual-monitor by creating a backing desk per second monitor page.
Monitor 2 paging was done by moving windows between backing and current desks.
I also used temp sticky for monitor 2 windows during monitor 1 paging.
See the 'ta/fvwmdx' branch in git for a module which does this but breaks
the FvwmPager.

Thomas Adam
elliot s
2016-05-24 19:23:45 UTC
Permalink
Post by elliot s
It looks like your code is doing ChangeButton colorsets also.
Is that a post 2.6.6 change?
Yes, on the master branch, will be in 2.6.7. No release date set for that,
but master should be stable, so I urge you to try it.
Since i wasnt running xinerama, i only had one "screen". So instead i
edited the c code to get the pagers/taskbars to look at only the
windows on their half of the page, by checking against window's x. It
would be nice if instead modules could be told which states to skip.
Then each window could dynamically control who uses it by setting
State.

Loading...