summaryrefslogtreecommitdiffstats
path: root/info/blueshift.texinfo
diff options
context:
space:
mode:
authorMattias Andrée <maandree@operamail.com>2014-09-07 14:50:15 +0200
committerMattias Andrée <maandree@operamail.com>2014-09-07 14:50:15 +0200
commit58fc31358cebb7f713b25608a0bc28fcda2b1958 (patch)
tree0e528e8d8ffd056fd79266adb33866a8846dcd47 /info/blueshift.texinfo
parentcleanup in preparation for and preparation for use of pylibgamma (diff)
downloadblueshift-1.90.tar.gz
blueshift-1.90.tar.bz2
blueshift-1.90.tar.xz
use pylibgamma1.90
Signed-off-by: Mattias Andrée <maandree@operamail.com>
Diffstat (limited to 'info/blueshift.texinfo')
-rw-r--r--info/blueshift.texinfo31
1 files changed, 1 insertions, 30 deletions
diff --git a/info/blueshift.texinfo b/info/blueshift.texinfo
index 89c7bde..d130bb3 100644
--- a/info/blueshift.texinfo
+++ b/info/blueshift.texinfo
@@ -1640,7 +1640,7 @@ curves) are @code{drm} and @code{drm_get},
respectively. The parameters are exactly the
same for the DRM functions as they are for
the RandR functions: @code{screen} is still
-named @code{screee} instead of @code{card},
+named @code{screen} instead of @code{card},
and @code{display} is still present but has
not effect.
@@ -1702,21 +1702,6 @@ GDI, except the functions are named
@code{quartz} and @code{quartz_get},
respectively.
-@c TODO resolve this (Windows and Mac OS X)
-Be aware than the following may change
-in a future version of Blueshift as support
-for Windows and Mac OS X increases.
-
-Both Windows GDI and Quartz have support
-for getting the number of available CRTC:s.
-It is however not as full featured as for
-RandR and DRM so @code{list_screens} cannot
-be used. Instead, use the functions
-@code{w32gdi_crtc_count} and
-@code{quartz_crtc_count}, respectively.
-They take no arguments and return an integer
-with the number of available CRTC:s.
-
Quartz also have support for resetting the
adjustment on each and every monitor on the
system to this on ColorSync. To perform
@@ -1724,20 +1709,6 @@ this action run the function
@code{quartz_restore}. It takes no arguments
and does not return any value.
-Again, the support for Windows and Mac OS X, is
-minimal. For now, if you want to use either of
-@code{w32gdi_crtc_count}, @code{quartz_crtc_count}
-and @code{quartz_restore} before Windows GDI
-or Quartz have been used via @code{w32gdi},
-@code{w32gdi_get}, @code{quartz} or @code{quartz_get},
-you will have to initialise them. The easiest
-way to do this is to just run @code{w32gdi_get}
-or @code{quartz_get}. Another way to do this
-is to run @code{w32gdi_open} or @code{quartz_open}
-and when done run @code{w32gdi_close} or
-@code{quartz_close}. Neither of these functions
-take any arguments nor returns any value.
-
@node Optimising
@section Optimising