Closed ajitid closed 1 month ago
Thank you for reporting. How many and how often have you sent the commands?
I'm just pressing my keyboard arrows to invoke them so really not too many. The easiest way to reproduce this is to first call monitorian /get with a display id followed by a monitorian /set with an id and do this again and again. Another thing that I've noticed is sometimes monitorian /get gives -1 as the brightness during these invocations.
If you just want to change the brightness from keyboard, keyboard shortcut is more appropriate. -1 means the value cannot be obtained.
What are the possible causes when value can't be obtained (cli gives -1 even when monitorian is properly functioning)?
A monitor is unexpectedly delicate. It easily fails to respond to a command typically immediately after power on and resume. It all up to each monitor.
Ah ok. I don't have anything else to add beside that I was using SDL2 and when I put a logic to cap framerate, the issue stopped happening. So I can't pinpoint what causes this really apart from the symptoms I described above.
PS: I have deleted my comment on Defer change until stopped. Feel free to delete yours too.
I am essentially calling
monitorian /set <displayid> <num>
command from Golang. And when I call it many times in succession I get this:After which calling monitorian commands from CLI doesn't give me any output. I have to restart monitorian to get output. The tray windows work as usual though.
I have a monitor attached to a laptop and both have separate working screens.