Thanks for the note. We did try in our beta to do this for "most" notifications but we wound up messing up the notification center pretty badly, so we stopped.

The interaction between "native" apps and the "modern" APIs is still a little difficult on Windows. For instance, we never had much luck handling notification clicks and other cases like that, especially if someone clicked a notifier after we updated.

We made the notifiers as they are to support Windows 7, and to handle the notifiers we make that animate over time (which isn't possible that I know of with the system). Then we wound up using them for everything due to the notification center problems.

Also we used every API we could to see if Windows is in "do not disturb" mode (presentation mode, fullscreen, etc.), and tried to suppress notifications -- there are like three different things we check there. I would assume that the "modern" side of Windows is not talking to the native side again there -- possibly even the "do not disturb" feature is quite new, since we shipped this version of f.lux.

Will look into it more.

While going through Flux's files I found a file called "flux.psd", it seems as though this is what defines the interface and its colours. I was able to change most of these to have a decent-ish dark theme. It's not perfect and may have some flaws, I haven't really bothered checking everything as I barely need the UI.

I'm not sure if linking edited files is allowed but here's the .psd

fwiw: I had the same experience with surface book, so there is a checkbox in the options menu to use the fn-lock'd equivalents, if that helps.

@ludi7 okay - how many apps are in your disable list, or do you reboot every day?

We should not be showing these more than once per session, and we'll make an option if it's too annoying.

Yes I think we have some more workarounds for issues with Fall Creators Windows 10 in the main build. I have been waiting for a new Windows release to stabilize before pushing a new Store update.

Just joined the beta, LOL,they're grabbing the wrong names for the devices. The menu just shows "Disable for Generic PnP Monitor" twice.

WMIMonitorID class has property UserFriendlyName, check script above. It's true I've found that not all displays have this property, the laptop's built-in display doesn't show up, so a fallback is needed.

Ok I fixed it - thanks. :)

There's nothing wrong with using both simultaneously. If you like it, do it.

Nvm, managed tô turned back to normal, but i Will never use this, again xd