summaryrefslogtreecommitdiffstats
path: root/info/blueshift.texinfo
diff options
context:
space:
mode:
authorMattias Andrée <maandree@operamail.com>2014-02-20 08:28:30 +0100
committerMattias Andrée <maandree@operamail.com>2014-02-20 08:28:30 +0100
commit2365e07c7226a1c3df702747378a0607d91fd995 (patch)
tree8dc94f14f7222af6101adb52c64b78b351959c39 /info/blueshift.texinfo
parentinfo: colour convertion (diff)
downloadblueshift-2365e07c7226a1c3df702747378a0607d91fd995.tar.gz
blueshift-2365e07c7226a1c3df702747378a0607d91fd995.tar.bz2
blueshift-2365e07c7226a1c3df702747378a0607d91fd995.tar.xz
m doc + applying adjustments
Signed-off-by: Mattias Andrée <maandree@operamail.com>
Diffstat (limited to '')
-rw-r--r--info/blueshift.texinfo18
1 files changed, 18 insertions, 0 deletions
diff --git a/info/blueshift.texinfo b/info/blueshift.texinfo
index a35044c..c376669 100644
--- a/info/blueshift.texinfo
+++ b/info/blueshift.texinfo
@@ -450,6 +450,24 @@ All these functions return lists with
the three colour components, not tuples.
Input and output is one colour instance.
+To apply a colour curve to the display
+server, invoke the @code{randr} function;
+@code{print_curves} can be used to print
+the curves to stdout instead (for debugging).
+These functions apply the curves to all
+monitors, put you can also use select monitors
+by specifying each monitor in as separate
+arguments. The monitors are indexed from zero.
+
+If you want to write your own curve flushing
+fucntion @code{translate_to_integers} can be
+used, it returned the colour curves converted
+from floating point lists to integer lists in
+a tuple of three (red, green and blue.) Replace
+the parameterless function @code{close_c_bindings}
+to make it free all used resource, this is
+invoked when Blueshift exits.
+
@node GNU Free Documentation License
@appendix GNU Free Documentation License