f.lux beta (another thread)


  • f.lux team

    Our new build 4.21 has some estimations for the circadian impact of your screen. Post bugs and discussion here! (The old thread was getting big so I made a new one).


  • Android

    Feedback on the Beta:

    1. I do not get up at the same time every day. This means the 'earliest wake time feature' is actually a hinderance.

    2. The interface has become exponentially more complicated - I really think you're going to lose the mass audience very quickly here.

    3. I don't like prompts telling me 'I'm getting sleepy' at 5pm. I'm not getting sleepy, and I don't wish to be told how I'm feeling.

    4. What are the purpose of all these whacky colour modes for which I cannot countenance a use? I can't help feeling the next update will be flashing disco lights and then all hope is lost.

    Thank you


  • f.lux team

    @dr_zoidberg590 Thanks for your thoughts on the beta.

    The earliest wake time is just that, the earliest time in the week you expect you'll wake up. This is based in the biology of the circadian melatonin rhythm, which requires strong periods of light and dark. Your sleep timing can be different every day, but your body is made to see light on a 24 hour rhythm.

    Also - you should not be getting a 'you're getting sleepy' prompt at 5PM unless you have some nonstandard wake times set up. Maybe there's a unique use case we should know more about here?


  • f.lux team

    1. (Wake Time Setting) Can you say why? Is it because you expect it to match your alarm clock and it doesn't, or because you just don't like the schedule?
    2. (Too complicated) I agree somewhat, and we are simplifying. It is harder to solve this problem if you consider how it actually affects a person, instead of picking nice colors. We have 100 years of artificial lighting that keeps people up too late, and it is a big project to change this. But with this direction, we are trying to move the public discussion away from pseudo-science and placebo, where it's trending right now.
    3. (Bedtime alerts) Do you have your wake time set to 2AM? Let us know something about your schedule and maybe we can help fix it.
    4. (Color modes) Actually, each color mode has a specific purpose, many of them for eyestrain during the day (so for most people they are not used everyday). We might need to make these settings use less space.


  • It would be good to have a manual "going to sleep time" (maybe next to the wake time in the interface) now that the days are getting longer there might be the need to got to bed while the sun is still up.

    And an app recognition for movie mode would be great, that turns it on automatically if for example VLC is running.



  • Updating to 4.21, I discovered that the application crashes consistently when closed. Which is not something I do very often, but since the installer closed it to update the files, the crash window popped up.

    I can reproduce this consistently, I just need to close the application from the system tray menu and I get two exception notifications. The first one is for a BEX event (buffer overflow exception) and the second is the resulting APPCRASH.

    The screen remains tinted, which suggests the crash happens before F.lux tries to transition back to the normal temperature. Happy to do more tests or send you logs if it helps.

    Also:

    • a more detailed changelog would help us give you better feedback!
    • interesting psd-based UI toolkit, is it a custom library?
    • the original thread is still stickied

  • f.lux team

    @dreadnaut Yes we will check it - are you using any home automation features? I know of one case where the hue pairing will crash if you exit too fast...


  • Android

    My wake time is set to 8:45am, so not sure why i got the alert at 5pm-ish. As for the colour modes, how is for example 'working late' different to just letting flux do it's normal cycle?

    It's kind of confusing to have the Custom colours drop-drown, but also Change Colour to... in the menu. It's not clear how they're different and there's no tooltip to explain what for example, 'far from the equator' is actually going to do.



  • @dr_zoidberg590 said in f.lux beta (another thread for 4.21):

    My wake time is set to 8:45am, so not sure why i got the alert at 5pm-ish. As for the colour modes, how is for example 'working late' different to just letting flux do it's normal cycle?

    It's kind of confusing to have the Custom colours drop-drown, but also Change Colour to... in the menu. It's not clear how they're different and there's no tooltip to explain what for example, 'far from the equator' is actually going to do.

    You can see the differences in the side of the UI that has the 3 sliders. Open the menu and choose "Adjust all colors at once". You can do this each time you choose a new preset to see what the differences are.

    When it says "Custom Colors", it means that you have chosen your own color temperature setup. The menu isn't called "Custom Colors". It will simply say whatever your current selection is (unless again you have set up your own color temperature settings).

    I think that it would be nice of "Custom Colors" were an available selection from the menu so that we can go back to our custom color setup.

    I personally feel that the "Change color to" menu is partly for fun while also being for specific purposes, like reducing eyestrain as herf said.

    Obviously though, you don't have to use features just because they're there (like "Change color to", or any of the presets, etc.). Michael and Lorna are simply trying to make an app that the majority will love and each person who uses it will have different things they love about f.lux and different ways to use it. So, if you don't have any need for a feature, then maybe just pretend it doesn't exist or something. I would bet that some people do use those colors or the presets, and if so, then hey great. I don't use them nor do I care for them.

    Really, I don't let f.lux do anything automatically because I don't need it to and I don't want it to. I even deleted the Registry subkey that makes f.lux start with Windows. So, I also ignore the wake-up time and the 3 different modes (Daytime, Sunset and Bedtime). Instead, I use f.lux for just 1 color temperature: 800K. I don't launch f.lux until I want 800K which means I don't have f.lux running in the background all day.

    So in other words, my use of f.lux is 100% "on-demand" - I do everything manually (well to me, "everything" is just one simple thing). I don't use any of the color presets or anything else. For me, f.lux is 800K, and 800K is f.lux. That's all I care about and that's all I need. I don't need the "Change color to" menu or the preset menu, or the option to use a wider slider range of 1200K - 9300K, I don't use Darkroom Mode, Movie Mode or anything. When I'm ready to end my day and begin winding down so that I can fall asleep easily, I simply open f.lux and it quickly warms the color temperature to 800K for me because I have all 3 modes set to 800K (Daytime, Sunset and Bedtime). The reason why is, I don't have a consistent day/night schedule. So my "day" is simply when I'm awake. Oh, and when I say it "quickly" warms the color temperature up, I mean it: I have the "Very Fast" transition speed set (but even that's not quite fast enough for me lol).

    For the record, I also switch my indoor lighting to low brightness pure red lights, I reduce my monitor's brightness to as low as it goes at this time and I also block out 100% of the light that comes in through my windows if there's any daylight out or if there will be daylight coming while I'm still trying to sleep (I use Blackout EZ Window Covers for that).

    What I'm really saying is, it sounds to me like most of the features in f.lux may be of no use to you. If so, then that's fine. Just ignore them and use f.lux the way that works best for you.


  • f.lux team

    @dr_zoidberg590 yes it shouldn't notify you at all until closer to midnight - if this happens again, please send a note.

    The goal of this interface is to make the schedule more customized over time while not overwhelming people with controls. So the main slider and the "change color..." selector are all about the current color, which is how we expect most people might think about it.

    I think we also probably did ok for advanced users ("setting up your friend's computer") with "All sliders at once" but we don't expect most people to use this, so we hid it just a bit.

    Then I agree with you that we don't visually distinguish between the presets pulldown ("set your whole schedule at once" or "undo the thing you did") vs. the rest of the adjustments ("what should happen right now"). We probably should think of a way to indicate that it's the whole schedule at once.

    One idea in the design is this: if you've never seen f.lux before and you've just installed at noon, you really can't guess how you want it to look at midnight. In most cases, you have to come back and do it later, or use a preset and hopefully our choices are good enough. But fine-tuning your midnight settings during the day almost always gets you to the wrong place, so we make it harder to do.



  • @herf said in f.lux beta (another thread for 4.21):

    @dr_zoidberg590 yes it shouldn't notify you at all until closer to midnight - if this happens again, please send a note.

    The goal of this interface is to make the schedule more customized over time while not overwhelming people with controls. So the main slider and the "change color..." selector are all about the current color, which is how we expect most people might think about it.

    I think we also probably did ok for advanced users ("setting up your friend's computer") with "All sliders at once" but we don't expect most people to use this, so we hid it just a bit.

    Then I agree with you that we don't visually distinguish between the presets pulldown ("set your whole schedule at once" or "undo the thing you did") vs. the rest of the adjustments ("what should happen right now"). We probably should think of a way to indicate that it's the whole schedule at once.

    One idea in the design is this: if you've never seen f.lux before and you've just installed at noon, you really can't guess how you want it to look at midnight. In most cases, you have to come back and do it later, or use a preset and hopefully our choices are good enough. But fine-tuning your midnight settings during the day almost always gets you to the wrong place, so we make it harder to do.

    Exactly. A super-warm color temperature during the day when you've only been awake for a few hours feels extremely different than it does when you've been awake for a long time and you need to go to sleep. So, testing settings during the day isn't as helpful as testing them when you want to be sleepy. When I choose like say 1200K but it's bright and sunny out, I might get the wrong that impression that 1200K will be waaaaay too much at night when I'm getting ready for bed.



  • I have some feedback about the new upper-right corner notification: I like the old one better because it had a much higher visibility. When this one comes up, I don't really notice it because it doesn't make me look at it like the old one did. When the old one came up, I felt automatically drawn to look at it. So, I think the best one is a very bright one with a big font, etc.

    The first time I experienced the new notification, I thought f.lux was broken because I thought nothing came up. So, I looked up where the notification should be and realized at that moment that f.lux has a new notification. With the old one, it almost forces the eyes to look at it as soon as it appears because we tend to instinctively look at things like that in our peripheral, like things that move or things that suddenly appear out of nowhere. This one doesn't grab my attention at all.



  • Installed version 4.21

    Issues that are gone:

    • When entering a game the screen went brighter (f.lux temperatures changed)
    • When closing f.lux i needed to wait 15-20 seconds in order to launch it again

    Now it keeps temperatures and i can close it and re-open right away. Good job.

    Just one note: Despite working as intended when launching games when you Alt + Tab you see the daytime (6500K e.g) temperature for like 1 sec and then it goes back (instant) to the right temperature (2000K e.g). Both sides, tabbing in and out.

    Another thing i noticed: when watching videos and entering fullscreen (i tested on youtube, twitch) screen goes brighter.



  • By the way, when taking screenshots or recording videos, this happens:
    http://i.imgur.com/EM9pnZF.png


  • f.lux team

    @disqQ yes we do this when you haven't rebooted yet, or when you're using a USB monitor.



  • @herf which situation are you talking about that requires a reboot? I don't use any USB monitors.


  • f.lux team

    Are we still asking for reboot at install? It should...



  • Well, I was too fast to say my problems went away with 4.21. It only worked once. :(

    Before I always had to open f.lux main window to make it update temperature to daylight when I started my computer in the morning. This morning, not even this worked. Now I had to take a slider and move it all the way to 5500k and the temperature was updated. Then I moved a slider back to 6500k.

    Could this be a problem with those old Radeon Catalyst drivers?

    Edit: Looks like that when I start computer it's always low temperature even if it was daylight 6500k when I last turned computer off. :/



  • @TwoCables Are you a Vampire? :D
    PS: I dont have 800k option....where can i enable it?



  • @sitayi2308 said in f.lux beta (another thread for 4.21):

    @TwoCables Are you a Vampire? :D
    PS: I dont have 800k option....where can i enable it?

    lol

    Use the new keyboard shortcuts ('hotkeys') for changing the color temperature. Come on. :)

    Hint: check out the f.lux options. Explore and discover. hehe

    Oh and Mike, see I'm not the only one who wants 800K. I think the main slider should have 1 range: 800-6500K. If the user wants higher color temperatures than that, then that should be an option they can enable. Or, they can just use keyboard shortcuts.



  • @herf No, version 4.21 installed and no reboot as required. Anyway i did reboot my system before writing those things here, so that's no the problem i guess.



  • Yeah, reboots aren't required for f.lux updates. Fresh installations of f.lux require a reboot though.

    Are you using a USB monitor?


  • f.lux team

    @disqQ Hmm we only use this transform when everything else has failed. That's usually when you have a device attached (like a docking station with USB/DisplayLink) that doesn't work another way. There might be bugs in the way we test the system though, so any more information about your configuration (GPUs and drivers and monitors and how they're connected) that would help.



  • @herf I have a GTX 1070 with drivers version 381.65. Using Dell P2414H with displayport.



  • @disqQ said in f.lux beta (another thread for 4.21):

    @herf I have a GTX 1070 with drivers version 381.65. Using Dell P2414H with displayport.

    Is this with Windows 10's Creator's Update too? I have seen several reports of problems since it came out, and each one was display-related in one way or another.



  • Yes, i'm using Windows 10 version 1703, build 15063.138.



  • @disqQ said in f.lux beta (another thread for 4.21):

    Yes, i'm using Windows 10 version 1703, build 15063.138.

    I thought so. :( Here we have yet another case of the Creator's Update causing problems.

    For the record, I have Windows 7. I'd bet though that I'd probably be experiencing some display-related problem too if I had Windows 10 and the Creator's Update. It seems that's pretty normal so far.


  • f.lux team

    Our NVIDIA (Kepler) machine is still on Anniversary (for displaylink testing) so I will try to make a build that prints out some internal state for you.



  • Thank you.



  • @TwoCables Thanks man, i didn´t know that. But...you are really a Vampire because 800k its too "bloody-style" :D
    PS: Im using 6500k during the day and have enable "reduce eyestrain" but i wonder if this option maintains during nighttime or it will disable itself.



  • @sitayi2308 said in f.lux beta (another thread for 4.21):

    @TwoCables Thanks man, i didn´t know that. But...you are really a Vampire because 800k its too "bloody-style" :D
    PS: Im using 6500k during the day and have enable "reduce eyestrain" but i wonder if this option maintains during nighttime or it will disable itself.

    I like 800K because I want to reduce all blue light when I want to get sleepy, not just most of it. It may look extremely red to you, but when I've been awake for a very long time, it's an extremely welcome thing and it no longer looks all that red (especially when there's no daylight coming through my window). I also switch to just one of these lights and nothing else:

    http://www.feit.com/led-lamps/performance/performance_led/performance_led/color_leds/color_led/a19-r-led

    When I'm maybe 30 minutes away from bedtime, I switch to this little thing:

    https://www.amazon.com/Westinghouse-03469-Nanolux-1-Watt-Bulb/dp/B000UQ1Y0Y

    If you're serious about your sleep, you get serious about everything that affects it. When I've been awake for a long time and I want to go to sleep in a couple of hours, it feels extremely good to go to 100% red light. Going from 6500K and a bright monitor to 800K and red indoor lighting and also a very dim monitor is a huge relief when I've been awake long enough to be extra sensitive to light.

    Check the curvy lines in f.lux to see how sensitive to light you're most likely to be when you've been awake for about 14-16 hours.



  • @TwoCables Man...you are amazing! Many thanks, im learning a lot with you!
    Ive been using F.lux since 2010 and can´t live without it anymore.



  • @sitayi2308 said in f.lux beta (another thread for 4.21):

    @TwoCables Man...you are amazing! Many thanks, im learning a lot with you!
    Ive been using F.lux since 2010 and can´t live without it anymore.

    You're quite welcome!

    Yeah, I think I've been using f.lux since maybe 2011. It's absolutely wonderful that I can still use my computer when I have successfully reduced or eliminated blue light and alerting light everywhere else in my little living space!

    Of course, I don't think it ends with light (or the brightness of light). I think it's also good to avoid loud noises and sounds, fast rhythms from anything, video games, movies, pretty much anything on T.V. these days including the news (heh), physical activity that raises your heart rate and gets you going, etc. Anything that is stimulating and energizing can be bad and make it harder to go to sleep. I mean, I think we should all take a cue from the animals outside because when the sunset draws near, they begin winding down and their activity levels decrease and they make less noise, etc. They calm themselves down and avoid things that interrupt that calm serenity they are trying to achieve.

    I even found in my research that it's best to wait a minimum of about 3 hours after eating before going to sleep because that's about the minimum amount of time for your stomach to become empty so that your body isn't being forced to digest while you are trying to sleep. Have you ever gone to sleep like say 30 minutes or an hour or an hour and a half after a decent-sized meal only to wake up hot or to have bad dreams - or both? Or you think you sleep fine but you feel kinda crappy the next day?

    Then, of course, there's caffeine and alcohol and other things. lol

    Of course, at 800K, there isn't much I can do on my computer and still enjoy it except for maybe reading things. That's fine though because I really shouldn't be doing anything other than super calm and peaceful things at that time anyway. Still, it's hard. I want to play video games or something so that the time goes by faster so that before I know it, I'm laying down to go to sleep. lol

    It's tough being a human being on this planet. LOL :)



  • On Windows, where is the disabled-program data stored? Since, currently there is no option to un-disable the use of f.lux with a certain program once it's been disabled for that program already.


  • f.lux team

    @SomeGuyNamedDavid Undo it the same way - open the program you want re-enabled, then open f.lux preferences > uncheck disable for [current app]. No master list yet.


  • f.lux team

    Before I update everyone, look at 4.22?

    https://justgetflux.com/flux-setup4-22.exe

    This one is all about color - we are trying to dial in better color calibrations even when Windows doesn't have one. Basically a lot of our laptops were too "green/yellow" and we tried to fix it using some embedded monitor info.

    Also trying to fix tone map so things look better when you dim a lot at night - looks amazing when it works.

    Color stuff may be buggy, so let me know! Options has "Use Monitor Data for Calibration" which you can turn off.



  • @herf Well....colors are more darker indeed :D can you explain what "Use Monitor Data for Calibration" means? I see little difference when I turn it off.


  • f.lux team

    @sitayi2308 Well most monitors have a built-in record of their chromaticities (the exact colors that RGB are).

    It used to be, this wasn't a good place to look for information, but with the half-dozen machines around here, we found awful color profiles but perfect embedded panel profiles. So we turned this on, and for some of our machines it is dialing in perfect colors.

    "dUV" is "distance from the planckian locus", or how far a thing is off the blackbody curve. So we had one particular laptop that was dialing in +0.016 dUV (way into the green/yellow area), and now it is around -0.001. So you would call it a beautiful warm glow, rather than puke yellow!



  • indeed darker color, Halogen turned Incandescent (Benq xl2730z)

    my feedback:

    1. can you please add an option for disable the Notifications on hotkeys actions? (alt page down, etc) In Overwatch when i change brightness the notification makes the game minimize and send me to desktop

    2. If i'm seeing it right each step on brightness is 7%, can it be a option to set how much % we want to each step ? I prefer small steps (on of the good things that SunsetScreen has) because this monitor brightness is weird (too dark or burn your eyes)

    thanks for the work !



  • Whoa. I think Alt+Page Down dimming looks much better. I mean, correct me if I'm wrong, but I think that previously dimming resulted in a severe gamma shift effect whereas now it's much more even from the top to the bottom of my monitor.

    I've been meaning to say that I think it would be great if f.lux could remember my last Alt+Page Down dimming setting. That way, if I restart my computer or exit f.lux and then relaunch it, it will go right back to where I had it. I always dim 1 or 2 increments when I go to an extremely warm red color like 800K because dimming with Alt+Page Down restores proper contrast at these extremely red colors with my preferred NVIDIA Control Panel "Digital Vibrance" setting. Obviously I could just stop using Digital Vibrance when I go to a very warm color like 800K, but it takes far more time than just pressing Alt+Page Down and the result is the same.

    I'd even say the Alt+Page Down dimming should never be undone unless the user chooses to do so, even if the computer is restarted (or if f.lux is closed and relaunched). So, I would even go as far as saying the dimming setting should always remain until the user restores the brightness with Alt+Page Up. After all, there is a "Return to Full Brightness" menu item now. Right now, the dimming is undone way too easily. It happens when I disable f.lux too.

    I think it would be nice too if we had the ability to dim from the f.lux menu or the window too. I think it would need to be a slider. Or, at least arrow buttons to click. Or, maybe just a drop-down menu of the different dimming levels. Or a sub-menu. Or both. Or all of these.

    I noticed too that Darkroom Mode gets disabled if I Alt+Page Up at all while in Darkroom Mode regardless of where my dimming is currently set. I don't know how long it has been like this though; this is the first time I think I've pressed Alt+Page Up while in Darkroom Mode. I would say that this isn't desirable. Of course, I could look at it as an easy way to disable Darkroom Mode. heh :)

    All transitions are now only super choppy if the f.lux window isn't open. So, all transitions are very close to being butter-smooth when the f.lux window is open, but once it closes (or if I close it), they become a slide-show every time I have a transition.

    I think the transition speed when launching f.lux to the set color temperature (like 800K for me) should be much faster. The transition speed for disabling and re-enabling is wonderfully fast, so I'd like it if the transition on the launch of f.lux (or when restarting the computer) could be that fast or faster.

    I think a restart is required after upgrading to 4.22. Before I restarted my computer, I was able to break the "Disable for [program]" feature by doing this:

    1. Enable "Disable for [program]" (in this example, I am using Firefox)
    2. Switch to Firefox to disable f.lux
    3. Open the f.lux window (f.lux remains disabled at this point)
    4. Go into the f.lux menu using the f.lux window and turn off the "Disable for [program]" feature

    When doing this, f.lux would get stuck at 6500K because it was still disabled for that program while I turned the feature off. After that, the feature no longer worked, even if I closed all programs and exited f.lux and reopened everything. Apparently, I had to restart my computer to fix it because I can't break it anymore no matter how hard I try.

    Before restarting my computer, I was able to Alt+Page Up in Darkroom Mode without disabling Darkroom Mode. Now it disables it.

    I don't know how to reliably reproduce this next bug, but sometimes the percentage of daylight will read 0% when I choose 1200K, and sometimes it will read 1%. Sometimes it seems to depend on how I chose the previous color temperature, whether that's via the menu or via the slider. Sometimes it seems to depend on whether I had 6500K selected prior to choosing 1200K, sometimes it doesn't. It's strange. If it reads 1% at 1200K, I can get it to go to 0% and stay there by Alt+Page Down dimming, and then Alt+Page Up to restore the brightness. Note: I am using the Very Fast transition speed, if it makes any difference.



  • So to add, I think a restart should be required for this update. Version 4.22 is working noticeably better for me after restarting my computer. When I installed 4.22, I still had 4.21 installed - but it wasn't running of course. I always exit f.lux first. So, it's not like I had a fresh installation of 4.22.



  • @TwoCables So far the only difference is more yellowish in all settings, so i presume thats the correct color when "Use Monitor Data for Calibration" its activated.



  • @sitayi2308 said in f.lux beta (another thread for 4.21):

    @TwoCables So far the only difference is more yellowish in all settings, so i presume thats the correct color when "Use Monitor Data for Calibration" its activated.

    I have no idea. That setting isn't changing anything for me.


  • f.lux team

    @TwoCables we turn it off internally when the monitor doesn't give good data or just reports sRGB. Probably should hide the checkbox then too.


  • f.lux team

    @TwoCables whether it says 1% or 0% is probably due to dimming - it should not care how you got there. And we aren't confident about these numbers to this level yet anyway!



  • @herf said in f.lux beta (another thread for 4.21):

    @TwoCables whether it says 1% or 0% is probably due to dimming - it should not care how you got there. And we aren't confident about these numbers to this level yet anyway!

    It's not due to dimming.



  • @lorna Bringing up the f.lux right-click menu while the program is launched doesn't show any disable options after the program has already been disabled.

    Though, on a separate note, I'd also like to see more options for how f.lux handles disabling-by-program. Currently, f.lux re-dims the color temperature as soon as the program window in question loses focus. Meaning that clicking in/out of the window frequently results in lots of temperature shifting. Either an option for "disable f.lux for out-of-focus programs" or a time-out period for f.lux's re-enabling (e.g. f.lux will wait 5 minutes after losing sight of the program before turning back on) would be great to see.



  • @SomeGuyNamedDavid said in f.lux beta (another thread for 4.21):

    @lorna Bringing up the f.lux right-click menu while the program is launched doesn't show any disable options after the program has already been disabled.

    Though, on a separate note, I'd also like to see more options for how f.lux handles disabling-by-program. Currently, f.lux re-dims the color temperature as soon as the program window in question loses focus. Meaning that clicking in/out of the window frequently results in lots of temperature shifting. Either an option for "disable f.lux for out-of-focus programs" or a time-out period for f.lux's re-enabling (e.g. f.lux will wait 5 minutes after losing sight of the program before turning back on) would be great to see.

    To put the disabled program back in the list, put it in focus and then open the f.lux menu or window. Then you can undo the disabling.



  • @TwoCables Alright, that worked, thanks. (Extremely prompt response, too!) There were difficulties in doing so because the window in question was in bordered fullscreen, meaning that the only way to get f.lux to see it was to open the f.lux window, click into the program in question, and tab back into the f.lux window before it closes. However, strangely, this method only works sometimes, rather than all of the time, so I may have to attempt it several times before the program in question will appear in f.lux's menu.

    Also strangely, the program in question appears in f.lux's menu twice when it does appear. Clicking the first one places/removes checkmarks on both, while clicking the second one does nothing.

    In the future, it might be better to have disable-able programs persist in f.lux's menu for a minute or so after they've been in focus, or to show the last few most recently in-focus programs in said menu, to prevent possible issues like these.



  • After what Lorna said in the post below, it sounds like they do have plans to make it far better.

    https://forum.justgetflux.com/post/13405

    "No master list yet."


  • f.lux team

    Yes this is still a work in progress. We held off on the feature in v3 because we didn't like the timing, which still needs improvement.

    I think we did a little better with the timing on Mac, where disable is very fast, but re-enable is very slow. The case for me is: working in Photoshop (disabled), alt-tab to a chat client (enable slowly), go back to Photoshop. Fast adjustments back and forth are not very good here.


Log in to reply
 

Looks like your connection to f.lux forum was lost, please wait while we try to reconnect.