[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freedesktop-openicc
Subject:    [Openicc] How to properly get the right _ICC_PROFILE_n (Was: Suggested update to "ICC Profiles in X 
From:       Tobias Ellinghaus <houz () gmx ! de>
Date:       2016-11-17 9:29:11
Message-ID: 1492086.KUoNRRt60N () liber
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Am Donnerstag, 17. November 2016, 07:40:15 CET schrieb Graeme Gill:
> Tobias Ellinghaus wrote:
> 
> Hi,

Hi and thanks for the reply. I guess I forgot to introduce myself, I am the 
author of that tool "darktable-cmstest" which started the discussion on the 
Argyll list. And I am happy to admit that I have no idea what I am doing there 
so every possible bug might be on my side. :-)

The code in question can be found here:

https://github.com/darktable-org/darktable/blob/master/src/cmstest/main.c

and can be compiled standalone without darktable. There is a comment how to do 
that.

> > The specification in its current 0.4 form calls for the screens to be
> > numbered in the Xinerama order.
> 
> I don't know what the definition of that is. Furthermore, since Xinerama
> doesn't have the concept of Outputs, I don't see how it can cover them.

I was just citing the specs.

> > In your proposed change you only mention the X11 Screen
> > index. I couldn't find any documentation to what that is. Do you have any
> > pointer to how to get that number?
> 
> Standard X11 screen_number, i.e. what's after the '.' in
> the DISPLAY environment variable. The 2nd argument to the
> XRootWindow() function. etc.

Is that enough though? What I see on my system (a laptop with external monitor 
attached) is that there is only one screen which has two outputs.

> Graeme Gill.

Tobias
["signature.asc" (application/pgp-signature)]
[Attachment #6 (text/plain)]

_______________________________________________
openicc mailing list
openicc@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/openicc

[prev in list] [next in list] [prev in thread] [next in thread]