To summarize, I have an application that runs on remote pi’s. If there’s a monitor attached it works like a kiosk, and users see a particular page. If there’s no monitor attached, it’s works as a little web server and remote users browse to it to see the same page. As the administrator, I Connect to those pi's, to verify what they're showing.
My problem is how Connect behaves very differently, and perhaps inconsistently, in those two cases.
If there is a monitor attached to the remote pi, Connect shows the remote desktop at whatever resolution is in effect on the monitor, as governed by the HDMI section of the kanshi config. If the Connect user resizes their viewing browser window, the image of the desktop gets bigger or smaller, like it's on a sheet of rubber, but the underlying desktop resolution is not changed. If it was 1920x1080, it stays that way. I like that one.
If there is NO monitor attached, the initial resolution of the remote desktop, as seen in Connect, should reflect the value in the NOOP section of the kanshi config. If the Connect user resizes their viewing browser window, the desktop resolution is changed to whatever fits into that changed viewing window, and the NOOP section of the kanshi config is rewritten accordingly. If the initial resolution was 1920x1080, it's now 1536x931, or some other weird value, unconstrained by any hardware or monitor or config. I don't like that one, at least with my app where the page is designed to display best at 1920x1080 and this change messes it up.
As to the apparent inconsistencies, there are cases where there is NO monitor attached, but changing the viewing browser window size does NOT change the remote desktop resolution. (I sort of like that one.) There are cases where there is no monitor attached, but the resolutions as offered in Control Centre are limited to 1024 or less. See posts above, or this post in the Trixie comments thread.
I would be very glad if someone could look into these inconsistencies.
I would be very very very glad if the Connect user were given a choice, say via a radio button on the Connect window, to display the remote desktop at a fixed resolution, as given by some value in the kanshi config, and NOT change that resolution when resizing the viewing browser window. In short, create an option to have non-monitor mode work like monitor mode.
My problem is how Connect behaves very differently, and perhaps inconsistently, in those two cases.
If there is a monitor attached to the remote pi, Connect shows the remote desktop at whatever resolution is in effect on the monitor, as governed by the HDMI section of the kanshi config. If the Connect user resizes their viewing browser window, the image of the desktop gets bigger or smaller, like it's on a sheet of rubber, but the underlying desktop resolution is not changed. If it was 1920x1080, it stays that way. I like that one.
If there is NO monitor attached, the initial resolution of the remote desktop, as seen in Connect, should reflect the value in the NOOP section of the kanshi config. If the Connect user resizes their viewing browser window, the desktop resolution is changed to whatever fits into that changed viewing window, and the NOOP section of the kanshi config is rewritten accordingly. If the initial resolution was 1920x1080, it's now 1536x931, or some other weird value, unconstrained by any hardware or monitor or config. I don't like that one, at least with my app where the page is designed to display best at 1920x1080 and this change messes it up.
As to the apparent inconsistencies, there are cases where there is NO monitor attached, but changing the viewing browser window size does NOT change the remote desktop resolution. (I sort of like that one.) There are cases where there is no monitor attached, but the resolutions as offered in Control Centre are limited to 1024 or less. See posts above, or this post in the Trixie comments thread.
I would be very glad if someone could look into these inconsistencies.
I would be very very very glad if the Connect user were given a choice, say via a radio button on the Connect window, to display the remote desktop at a fixed resolution, as given by some value in the kanshi config, and NOT change that resolution when resizing the viewing browser window. In short, create an option to have non-monitor mode work like monitor mode.
Statistics: Posted by tinker2much — Thu Oct 09, 2025 6:55 pm