Sort of true.There is only one frame buffer. So once the issue with wayfire is fixed you should be able to have one window filling this single frame buffer and then being output on whatever no of screens your system is using.Okay, thanks so much for your input so far!
To clarify my use case: I want to create a narrow, but ultra-tall display which will show a web page in kiosk mode. Therefore dragging the window across both screens or using two separate windows in full-screen mode is not an option.
I understand that OS, drivers, window managers etc all have their own restrictions, and I'm not assuming what I want to do is possible, but I want to give it a try. Therefore, my current approach is "making the window manager believe that there is only one very tall display" so that I can use the "normal" full-screen function to spread the brwoser window across both pysical displays.
Having the physical displays configured as extended desktop and using two browser windows in full-screen mode is my "known-to-be-working" fallback, but I'm interested in pushing the boundaries a little here (if possible).
I'll have another go at it using X11 / xrandr, will report back if I get some results.
DRM emulates the old fbdev API, but only creates one /dev/fbN node per DRM card. X11 and Wayfire totally ignore this.
X11 creates one buffer that covers the whole extended desktop, and then tells each DRM device which bits of it to render.
Wayfire creates individual buffers for each display, and renders them independently. That is why the window disappears from one of them when it is split over two (or more) screens.
Windowing systems know about each screen, so hitting the fullscreen button will maximise to the size of the current screen, not the full extended desktop. To get that arrangement will always require manual intervention.
Statistics: Posted by 6by9 — Thu Feb 22, 2024 11:22 am