Dual-screen support was working in cinCV at least
Managed to get qemu (v7.2.0-334-g959b27f577-dirty) running with two virtual displays qemu-system-x86_64 -enable-kvm -m 2000 -cpu qemu64 -device virtio-vga,max_outputs=2 -device virtio-vga -cdrom /home/admin/CDROM-4.14.246-big-7.iso -smp 2 -device usb-mouse -M q35 -usb then in running system I run xconf (script configuring X from old Slax 6) and then startx bring me two displays. first i send xterm to second display by using DISPLAY=":0.1" from there I launchd cinelerra I typed :0.0 in CinCV's output config tab, and on next startup Compositor was on original first display..
On 1/8/23 20:14, Andrew Randrianasulu wrote:
Managed to get qemu (v7.2.0-334-g959b27f577-dirty) running with two virtual displays
attached JPGs demonstrate that regardless of the playback-X display selected, the GUI windows will only display on :0.0. I tried starting the app from both :0.0 and from :0.1 with same results. GUIs seem locked to :0.0 I must question the meaning of playback-X...what is that suppose to mean/do? More descriptive field would be "compositor display :0.0"
пн, 9 янв. 2023 г., 04:57 Rob Prowel <rprowel@comcast.net>:
On 1/8/23 20:14, Andrew Randrianasulu wrote:
Managed to get qemu (v7.2.0-334-g959b27f577-dirty) running with two virtual displays
attached JPGs demonstrate that regardless of the playback-X display selected, the GUI windows will only display on :0.0. I tried starting the app from both :0.0 and from :0.1 with same results. GUIs seem locked to :0.0
well, I send ALL windows once to second monitor by playing with main window menu items 'Send windows left/send windows {to monitor} Right' but then getting them back was impossible without editing Cinelerra_rc on cingg compiled 1 nov 2020, so if it was a regression it was not very recent one? I used just X -configure (X version 1.19.7) as root inside qemu VM launched as described above, then copied xorg.conf.new to /etc/X11/ as xorg.conf and made sure there was no files in /etc/X11/xorg.conf.d X started with kde 3.5.10 on both screens (not sure if fluxbox handles this...?) so I guess adding printfs to print what each window get as DISPLAY argument will be next step ....
I must question the meaning of playback-X...what is that suppose to mean/do? More descriptive field would be "compositor display :0.0"
пн, 9 янв. 2023 г., 04:57 Rob Prowel <rprowel@comcast.net>:
On 1/8/23 20:14, Andrew Randrianasulu wrote:
Managed to get qemu (v7.2.0-334-g959b27f577-dirty) running with two virtual displays
attached JPGs demonstrate that regardless of the playback-X display selected, the GUI windows will only display on :0.0. I tried starting the app from both :0.0 and from :0.1 with same results. GUIs seem locked to :0.0
I must question the meaning of playback-X...what is that suppose to mean/do? More descriptive field would be "compositor display :0.0"
I *think* this part of cingg was rewritten so it will be possible to send all windows to specific (non-xinerama, so not draggable) screen. I guess way to add back compositor display setting is to add two more preferences and functions in mainwindow and cwindow (like it already done, but slightly differently named) plumbing this setting to cwindow's init function .... I'll try to cook something.
participants (2)
-
Andrew Randrianasulu -
Rob Prowel