Skip to content
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

[QUESTION] How to disable DDC? #275

Closed
jclsn opened this issue Mar 3, 2023 · 8 comments
Closed

[QUESTION] How to disable DDC? #275

jclsn opened this issue Mar 3, 2023 · 8 comments

Comments

@jclsn
Copy link

jclsn commented Mar 3, 2023

I would like to keep my external monitor from dimming and can't find the setting. Is there a possibility without recompiling?

@FedeDP
Copy link
Owner

FedeDP commented Mar 3, 2023

Hi! At the moment this is not possible; however I was recently thinking about allowing that, since I am refactoring that part of code in Clightd.
So, look forward for the next Clightd release for that :)

@FedeDP
Copy link
Owner

FedeDP commented Mar 3, 2023

This commit: FedeDP/Clightd@932ea16 fill fix the issue :)
You will have a way (using an env variable) to disable Clightd DDC support.

@jclsn
Copy link
Author

jclsn commented Mar 10, 2023

Great, can you make it possible from the config? That would be a bit more convenient imo

@FedeDP
Copy link
Owner

FedeDP commented Mar 10, 2023

Well i can't add that to the Clight config because there is no way to set an env variable to an already running process.
The systemd unit for Clightd will be easily customizable though; i will make sure to update Clightd wiki pages (and add an entry in the Clight FAQ) once the PR is merged!

@jclsn
Copy link
Author

jclsn commented Mar 10, 2023

Okay, just modify the service file then. Will try that when it bugs me the next time. I never got why you are shipping clight in two packages anyway. I mean, the daemon could just get installed along with with clight

@FedeDP
Copy link
Owner

FedeDP commented Mar 12, 2023

I never got why you are shipping clight in two packages anyway. I mean, the daemon could just get installed along with with clight

Yep, that would work fine, and perhaps it would be easier to ship it.
At the same time:

  1. I don't want Clightd to be completely tied to Clight (everyone can write an user service that uses Clightd as a backend, and i don't want to stop anyone from doing that). Of course, you could do it even if Clightd was bundled with Clight, but then it would tie them together too much imo
  2. I don't want their release cycles to be tied; instead, i want to be able to focus on eg: Clight for a couple of months, and then release it, without caring about Clightd. Nowadays, i have very limited time to work on my side projects therefore it is much easier for me to manage them in this way.
    Of course, sometimes a new Clight feat depends on a new Clightd feat, and then their development cycle is tied, but i can't do much about that :D

@jclsn
Copy link
Author

jclsn commented Mar 12, 2023

Okay, yeah organizing the code well is a good idea. From that perspective it makes sense. Thank you for clearing that up! :)

@FedeDP
Copy link
Owner

FedeDP commented Jun 7, 2023

Clightd PR Is now merged :) and clightd wiki Page updated: https://github.com/FedeDP/Clightd/wiki/Backlight. I think we can close this one.
The environment variable is named "CLIGHTD_BL_DDC_ENABLED"!

@FedeDP FedeDP closed this as completed Jun 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants