search

rockowitz / ddcui

Graphical user interface for ddcutil - control monitor settings
http://www.ddcutil.com
GNU General Public License v2.0
147 stars 2 forks source link

add command line options to executed command #31

Open fischer-felix opened 2 years ago

fischer-felix commented 2 years ago

Would it be possible to add options (e.g. --noverify) to the executed command in the background, since my monitors only actually do anything if you add --noverify?

rockowitz commented 2 years ago

First, I assume you're referring to the 0.2.0-dev branch of ddcui. Release 0.1.0 is ancient.

Second, it is possible to pass options directly to shared library libddcutil using a Configuration File. Most ddcutil command line options, other than those for feature or display selection, can be specified there.

However, I don't think this would address your concern. ddcui explicitly disables verification on the API call that sets a feature value. However, it does immediately read the value in a separate operation so as to display the proper value in the UI. In general it can't assume that the monitor has performed a requested action.

I'd like to better understand your problem. What are the manufacturer/model of your monitors? Since you refer to option --noverify, I assume you need to use this on the ddcutil command line when issuing the setvcp command. Let's assume for the sake of specificity that you're changing the brightness (feature x10). Are you saying that the perceived brightness doesn't change unless --noverify is specified, or that the perceived brightness does change, but the setvcp command reports that verification has failed. If the latter, does a subsequent getvcp report the changed value or the original value? Does the value change in the OSD?