@Rouxbourbon f.lux has an options to "Always use Windows internal color table" which emulates Night Light, so this might be a workaround.

Changing screen colors is unfortunately not a very good place to run multiple apps at the same time, as the order of what should go first is not defined.

@Quincel yeah they are becoming upsettingly rare on modern laptop keyboards. A few thoughts:

Since most laptops have "brightness" keys already, we did not work very hard at finding an alternative for laptops. The trouble with hotkeys generally is that it is very hard to find one that doesn't conflict with another app.

We do support "surface keys" which allows Alt+F11 and Alt+F12 to do the same thing - you have to turn it on in f.lux options.

In a pinch, you might be able to get an app like AutoHotKey to alias those keys that we register

@spaceowl I think you are right here - the code used to look at window titles for this, but it doesn't do this anymore. The behavior you're seeing was for better matching of apps that put their name in the title (with the name of a document or something alongside), but it looks like we stopped doing this some time ago.

I will make a change in the next beta and we'll see if anything breaks. thanks!

+1 for this issue. I applied the registry flag mentioned above and while the Windows setting does change properly, the UI doesn't. 1855444f-4235-4530-8a96-00c33959110c-image.png

A workaround is to use the open source app "AutoDarkMode" to handle theme switching and disable the option in f.lux. It would be nice to have this work properly in f.lux to reduce the need for extra apps.

@DCRnash We did this on old dual-GPU macs from the 2012-2015 era. We found they would switch from discrete to integrated GPU and load the system colors, but not the f.lux ones.

On newer Apple Silicon macs, there is no switch (since there is just one GPU) and so we don't have to build a profile to keep things working. It's better in most cases for f.lux to be a "temporary" effect. But in case you somehow wanted the old behavior, it might still work with a pref - check out: https://justgetflux.com/news/2014/10/28/profile.html

@Sreten you are right that not all of these appear on the Mac, we will make a note to add them in the future

@f-lummoxed good memory, there was an easter egg and it needs two things:

the Preference in the registry* for "candle" has to be turned on you have to hit the 'c' key while the f.lux UI is up

It got turned off during one of our "don't do things that the user can't figure out how to undo" cleanups... but the pref is still there.

HKCU\Software\Michael Herf\flux\Preferences\candle = REG_DWORD(1)

@ahartline808 yes it will prompt until you give it a location, but if you use the "working late" preset it will not pay attention to solar time. It's probably easier to give it the location and then use a preset that ignores it.

@Moisey we currently don't test DisplayLink on macOS, but we might in the future.

@cxuj6464 It really depends on what the GPU manufacturer is doing (sometimes things break in driver updates since Win7 was EOL in 2020) - I would try a few different drivers (maybe older ones) to see if Win 7 support still works using those.

@fluxhelpme yes you can set the wake time one hour earlier for now.

@rich-vine1252 there is a toggle in the "f.lux > Color Effects" menu that makes f.lux do this switch automatically. It should be off by default, but it sounds like you want to make sure it is off on your Mac also.

@Alfal yes this is a known issue and reported to Microsoft - we usually see it happen once per f.lux session.

@guillaume1978 this is because the dock does not provide traditional color controls, so f.lux has to emulate them using the GPU.

If the dock happens to be a DisplayLink one, you can sometimes add these controls back using the registry: https://support.displaylink.com/knowledgebase/articles/1886413-how-to-enable-night-light-or-f-lux-on-displaylink