summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--info/blueshift.texinfo18
-rw-r--r--src/monitor.py3
2 files changed, 20 insertions, 1 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
diff --git a/src/monitor.py b/src/monitor.py
index 595d2b7..f50c9dc 100644
--- a/src/monitor.py
+++ b/src/monitor.py
@@ -31,7 +31,8 @@ def translate_to_integers():
'''
Translate the curves from float to integer
- @param :(int, int, int) The red curve, the green curve and the blue curve, mapped to integers
+ @param :(list<int>, list<int>, list<int>) The red curve, the green curve and,
+ the blue curve mapped to integers
'''
R_curve, G_curve, B_curve = [0] * i_size, [0] * i_size, [0] * i_size
for i_curve, o_curve in ((r_curve, R_curve), (g_curve, G_curve), (b_curve, B_curve)):