rockowitz

On 1/15/20 9:59 AM, haarp wrote: > > Cheers, those notes sounds familiar. Looks like DDC is hell of a mess > of poorly implemented specs. > Poor implementations, and...

Desktop and appstream files are in the upcoming 0.2.0 release.

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...

First, I assume you're building from branch 0.2.0-dev, which will soon be released. The master branch is ancient. If class Monitor lacks a vtable something has gotten out of sync...

Use ddcutil branch 1.1.1-dev, which is the current development branch.

On a hunch that there are 2 definitions of class Monitor at compilation time, I have replaced all forward declarations "class Monitor" in header files with "include base/monitor.h", and uploaded...

You are quite right about the vtable problem being the result of monitor.h not being processed by the MOC. I owe you an apology for your effort. I forgot that...

The latest updates to branch 0.2.0-dev add src/base/monitor.h to the source file list for set_executable(), and eliminate the symbolic link hack from src/main/monitor.h to src/base/monitor.h. Please rerun cmake (and of...

You're pointing to buttons whose text is hardly legible.  This is a problem with the Qt theme. I see it on many application/distribution combinations, e.g. VirtualBox. Trying to properly cope...

@gaborbernat As @aryoda says, I really need to know what steps are confusing, and what error messages you're seeing. At this point you should be using at least release 1.0.1...