cold start
Opened this issue · 1 comments
532910 commented
If started with monitor switched off (via ssh -X for example) it will always report Display does not support DDC
even after turning it on. The only way is to restart application.
rockowitz commented
Unfortunately, ddcutil only performs monitor detection at startup. This
is not a problem for the command line version, which just detects
monitors, performs an operation, and terminates. It is a known issue
for ddcui. In the best of worlds, the library would detect a monitor
change, scan the new monitor, and notify ddcui of the change. Simpler
to implement, but still requiring API enhancement, would be a Rescan
Displays entry of the Actions menu. It's on the TODO list - the GUI
hooks are already there.
…On 9/27/19 4:46 PM, sergio wrote:
If started with monitor switched off (via ssh -X for example) it will
always report |Display does not support DDC| even after turning it on.
The only way is to restart application.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#15?email_source=notifications&email_token=ADMGY3RJYCUMXMJTS7LQYPDQLZWLZA5CNFSM4I3KXNJKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HOH6LPA>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADMGY3WYCPXLNWL274FVEJDQLZWLZANCNFSM4I3KXNJA>.