[argyllcms] Re: dispcal too quick for my monitor

  • From: Torsten Bronger <bronger@xxxxxxxxxxxxxxxxxxxxx>
  • To: argyllcms@xxxxxxxxxxxxx
  • Date: Wed, 17 Jul 2013 21:30:21 +0200

Hallöchen!

Graeme Gill writes:

> Torsten Bronger wrote:
>
>>> I can add code to use XRandR V1.3 XRRGetScreenResourcesCurrent()
>>> when available if that makes any difference ?
>> 
>> I cannot tell, I'm not in this topic deeply enough I'm afraid.
>
> Source code here for a version that uses XRRGetScreenResourcesCurrent():
> <http://www.argyllcms.com/Argyll_dev_src.zip>

While dispwin indeed causes no blackout anymore, I still could not
"profile" and "report on uncalibrated display device" in dispcalGUI.
The following addition enabled me to use Argyll fully:

diff -Naur Argyll_V1.6.0_beta/spectro/dispsup.c 
Argyll_V1.6.0_beta_new/spectro/dispsup.c
--- Argyll_V1.6.0_beta/spectro/dispsup.c        2013-07-16 04:53:19.000000000 
+0200
+++ Argyll_V1.6.0_beta_new/spectro/dispsup.c    2013-07-17 21:28:43.279161848 
+0200
@@ -2350,6 +2350,7 @@
                /* Close the positioning window */
                if (p->dw != NULL) {
                        p->dw->del(p->dw);
+                       sleep(7);
                }
        
                /* Open display window again for measurement */

-- 
Torsten Bronger    Jabber ID: torsten.bronger@xxxxxxxxxxxxxxxxxxxxx
                                  or http://bronger-jmp.appspot.com


Other related posts: