-
-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to change the remembered display monitor to record from is not entirely clear #286
Comments
There should be a reset button beside the Record button that will be appear when you have chosen to remember the last source. |
With current UI and size constraints, I'm not sure how to improve its discoverability. However, there is #263 which also aims to improve discoverability. |
Oh, I feel silly for not figuring out that was what this button does. It's also very unremarkable because of the icon-only "refresh" icon metaphor. I wondered whether it should always prompt for the desired screen when there are multiple screens instead (I rarely want to record from the same screen from one day to another), but I guess a UI like #263 proposes would solve this anyway! |
That sounds a good idea, but not sure if it is possible to reliably get the number of monitors. Also, not sure how it would work if window recording is enabled. |
Affected version
2.2.4 from flathub
Bug summary
On a computer with multiple displays, especially when recording a region of the screen, Kooha will prompt you through a screensharing portal which screen and region to use.
However, by default it has this "[x] Remember display selection" (or whatever) checkbox enabled... and if you don't pay enough attention, or your situation changes later down the road, you are stuck: you cannot ever record the contents of a different monitor.
Short of being able to offer a UI like GNOME Shell's built-in screencaster, there ought to be some sort of way in Kooha's menus/preferences to reset this, or to choose the display…
The text was updated successfully, but these errors were encountered: