rthardy
commented
6 years ago So...some questions if I could:
- It looks to me like you, @beku are the owner of OpenICC. Is that correct?
- This version of xcalib looks like the source, or as close as possible to the one in my openSUSE distribution. Anything to that?
- I would like to see the spacing change, but am not so sure of the "monotonic" change; should they be in separate pull requests.? In any case this is my first venture into Github, or even git, so how did I do?
I've been thinking about more extensive changes:
- Figure out why I have "768 colors lost" in a flat 1024 entry table.
- Eliminate the "-a" requirement and simply read a profile if it is offered.
- Eliminate the "monotonic" warnings altogether in favor of a slightly more detailed "xcalib -l -a" summary.
The reason for that last is modifying an inverted ramp makes as much sense to me as modifying any other ramp. It happens a quarter of the time when I run the following script
#!/bin/bash
if test -f ~/.inverted-display; then
if test -f ~/.altered-display; then
xcalib -c; #this is a normal display
rm ~/.inverted-display ~/.altered-display;
else
xcalib -co 66 -a; #nighttime away from city lights
touch ~/.altered-display;
fi
else
if test -f ~/.altered-display; then
xcalib -c; #nighttime inverted display
xcalib -red 0.7 0 100 -green 0.7 0 84 -blue 0.7 0 67 -i -a;
mv ~/.altered-display ~/.inverted-display;
else
xcalib -gc 2.2 -a; #high gamma for incident sunlight
touch ~/.altered-display;
fi;
fi;I've been using some version of that script for years, now.
beku
Tab use (control character) was inconsistent and unnecessary, and causes warnings in plotutils, e.g.; xcalib -p -a | grep ^[0-9] | graph -a -T X -x 0 3071 -y 0 65535 -m 0 -X "$(xcalib -l -a | tail -n 1)"