search

cynthia / blacktree-nocturne

Automatically exported from code.google.com/p/blacktree-nocturne
1 stars 0 forks source link

Nocturne "Tint Colors" conflict when running "F.lux" #66

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Run both Nocturne (2.0.1) and f.lux (v. 23) 
2. Open Nocturne Preferences and check "Tint Colors"
3. Press "Switch to Night"

What is the expected output? What do you see instead?

I expect to see the selected tint applies to the "Night" screen
Instead the tint appears briefly and reverts to the normal inverted colors.

What version of the product are you using? On what operating system?

Nocturne (2.0.1) and f.lux (v. 23)  on OSX "Mavericks" 10.9.1

Please provide any additional information below.

http://justgetflux.com/

Original issue reported on code.google.com by z...@zmix.net on 12 Jan 2014 at 2:11

GoogleCodeExporter commented 9 years ago 
Can you confirm that Nocturne tints colors  without crashing when f.lux is not 
running?  I can reproduce the tint crash without f.lux in Mavericks (see issue 
63, issue 64)

Original comment by And...@hunt.li on 28 Jul 2014 at 1:14

GoogleCodeExporter commented 9 years ago 
I just tested and confirmed that Nocturne tint's the colors properly when f.lux 
is not running.

Original comment by z...@zmix.net on 28 Jul 2014 at 2:33

GoogleCodeExporter commented 9 years ago 
tl;dr: My guess is that both F.lux and Nocturne use the same Core Graphics 
interface to tint the color of the screen TO a value, and not BY a value.  So 
without being made aware of each other, they cannot layer their effects.

While F.lux might be listening and adjusting the display color pretty 
constantly (checking the current time and light-levels?), Nocturne only adjusts 
the state when it's toggled.  

If you disable F.lux from its menu (e.g. for an hour), Nocturne will be able to 
tint correctly.  I suspect that means that when you disable F.lux, it stops 
trying to constantly set / reset the tint.

Assuming the above is true, I don't think there's a way to reconcile the two 
programs.  Each of them are designed to set the tint of the screen to a certain 
color, not alter the current screen by a delta.  E.g:  rather than taking the 
current tint (whatever it is) and making it redder / inverting it, they take a 
preset value of red and set the screen color to that.

Original comment by And...@hunt.li on 1 Aug 2014 at 3:20