Limitation of Capture Cursor

[PeterWang-dev]

Nothing happened after ticking [x] Capture Cursor .

OS: Arch Linux
DE: Plasma 6.2.0
Display Protocol: Wayland
Version of Weylus: master branch

[PeterWang-dev]

I have done some investigations and tracing. There's a very weird thing I've noticed is that capture_cursor variable seems being ignored in PipeWireCapturable::recorder .

Weylus/src/capturable/pipewire.rs

Lines 108 to 111 in 8d06299

	fn recorder(&self, _capture_cursor: bool) -> Result<Box<dyn Recorder>, Box<dyn Error>> {
	Ok(Box::new(PipeWireRecorder::new(self.clone())?))
	}
	}

[PeterWang-dev]

It seems a known limitation. Users need to refresh the source list to apply the state change of Capture Cursor.
Any further re-design of this? @H-M-H

[H-M-H]

Thanks for the report! Your observations are correct! On Wayland screen recording works by first requesting permission from the user. This typically shows a dialog asking for permission. This request is also the place to specify if the cursor should be recorded. This means if the capture cursor setting is changed, Weylus would have to ask the user for permission once again. So if you want to capture the cursor you have to:

• check the checkbox
• reload the list of windows/screens
• choose the desired window/screen

Obviously, this is not very nice. I am open for ideas to properly deal with this.

Another option I have not yet considered is requesting cursor metadata as described here: https://flatpak.github.io/xdg-desktop-portal/docs/doc-org.freedesktop.portal.ScreenCast.html#org-freedesktop-portal-screencast-availablecursormodes