You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I like the functionality of kdisplay and would like to use it as my display management tool instead of kanshi/wdisplays/wlr-randr.
Is there some persistent process I can run that will apply kdisplay profiles on compositor startup / output hotplug? If not, is there a command to apply kdisplay config without showing pref UI?
Thanks!
The text was updated successfully, but these errors were encountered:
Hi, some documentation you can find in the Disman readme. Under wlroots-based compositors you would need to run it "independently", that means the Disman backend daemon must be started on session start. It will then optimize and load configs automatically. You would then just execute KDisplay for changing configurations, which connects to this daemon.
Follow-up questions to improve our documentation:
Have you known about this section in Disman's readme? If not, is it difficult to find because the KDisplay readme doesn't mention it under "Usage"?
Is the description in the Disman readme clear about running it independently? Maybe we should provide a sample systemd unit file.
In GitLab by @edrex on Aug 23, 2021, 24:55
Hi, I like the functionality of kdisplay and would like to use it as my display management tool instead of kanshi/wdisplays/wlr-randr.
Is there some persistent process I can run that will apply kdisplay profiles on compositor startup / output hotplug? If not, is there a command to apply kdisplay config without showing pref UI?
Thanks!
The text was updated successfully, but these errors were encountered: