Release 0.5.4

ddcui release 0.5.4 contains a single change. As part of package installation, file /usr/lib/modules-load.d/ddcui.conf is installed, ensuring that module i2c-dev is loaded.

For details, see file CHANGELOG.md or the ddcutil website.

Release 0.5.3

ddcui in release 0.5.3 requires requires libddcutil 2.1.3 or later.

Release 0.5.2

ddcui release 0.5.2 clears out some remaining debug code and ensures that display status change detection is enabled only for connection and disconnection events. DPMS status changes are ignored.

For details, see file CHANGELOG.md or the ddcutil website.

Release 0.5.0

ddcui release 0.5.0 requires libddcutil.so.5.1 from ddcutil 2.1.0 or later.

There is one major change in this release. ddcui (using libddcutil) watches for display connection and disconnection.

For details, see file CHANGELOG.md or the ddcutil website.

Release 0.4.2

This ddcui release requires libddcutil.so.1.5.0 from ddcutil source package 2.0.0.

For details, see the file CHANGELOG.md in the source tree or the ddcutil website.

Release 0.3.0

General User Interface Changes

• CTL-Q terminates ddcui (does not apply within dialog boxes)
• Errors opening /dev/i2c and /dev/usb/hiddev devices are reported using a message box instead of being written to the terminal. These errors typically reflect lack of permissions (Linux error EACCESS).
• Optionally requiring the control key to be pressed when changing feature values now applies to all changes, not just those made using sliders. (The option is set using command line option --require-control-key or the UI Options dialog box.).

Feature Value Handling

• For simple NC values, do not include the SH field in validation when changing a value. It has been observed that there exist monitors (e.g. Dell U4320) for which the high order byte of feature x60 (Input Source) can be non-zero.

EBUSY Errors

• As of libddcutil release 1.3.0, the shared library has been modified to avoid the code path in driver i2c-dev that can produce EBUSY errors. Options --force-slave-address and --disable-force-slave-address, introduced in Release 0.2.1, are deprecated and no longer have any effect. For details see Device Busy (EBUSY) Errors in the release notes for ddcutil 1.3.0.

For a more detailed description of the changes in this release, see file CHANGELOG.md in the source tree or section ddcui Release Notes on the web site.

Release 0.2.1

ddcui 0.2.1 better handles API calls that fail with Linux errno EBUSY. This occurs if DDC communication with a display is blocked by some other program, notably display driver ddcci.

• Displays that are busy are reported as such in the Summary view, instead of being marked invalid.
• Similarly to program ddcutil, command line option --force-slave-address enables ddcui to override the other program's hold on the display. For details, see See Option: --force-slave-address and section Device Busy Errors in the ddcutil 1.2.2 Release Notes.

Command line option --use-latest-nc-values and the corresponding checkbox in the NC Feature Values dialog have been removed. Instead, use the User Defined Features facility to define non-standard values for a monitor feature.

cmake control file CMakeLists.txt has been cleaned up.

• Better support for controlling build type through use of cmake variable CMAKE_BUILD_TYPE. The default is value RelWithDebInfo.
• By default, if ccache exists on the system it will be used to speed build times.

For a more detailed description of the changes in this release, see file CHANGELOG.md in the source tree or section ddcui Release Notes on the web site.

Release 0.2.0

Release 0.2.0 represents a major step in ddcui development. While still beta level code, it should be usable by and useful to most people.

ddcui 0.2.0 requires at least libddcutil.so.4.1.0 from ddcutil package 1.2.0 or later.

Release 0.1.2

ddcui 0.1.2 is an emergency bug fix release.

Combo boxes for simple Non-Continuous features were blank instead of showing the current and allowed values.

Release 0.1.1

ddcui release 0.1.1 adds additional features and has numerous changes in the "fit and finish" category. In particular:

• Command line options have been added for starting ddcui, corresponding to settings in the Option dialogs, and (if multiple monitors are found) the initial monitor selected.
• Command line options have been added for tuning libddcutil, corresponding to ddcutil command line options.
• The Feature Selection Dialog, along with command line option --custom-feature-set,
  enable the user to specify the VCP features to be shown.
• Better handling of error conditions
• Better Help text

ddcui version 0.1.1 requires ddcutil version 0.9.9.

For general information about the graphical user interface, see ddcui.

For a complete list of changes and bug fixes, see Release Notes for ddcutil 0.9.9 and ddcui 0.1.1.