f.lux beta (another thread)
-
@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.
-
@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.
-
@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."
-
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.
-
@herf Alright, sounds great, will be looking forward to it. Keep up the good work, been loving much of the new beta changes so far.
-
@SomeGuyNamedDavid Not while it's launched, while it's active. Thanks @TwoCables for making that more clear.
@lorna
-
@lorna said in f.lux beta (another thread for 4.21):
@SomeGuyNamedDavid Not while it's launched, while it's active. Thanks @TwoCables for making that more clear.
You're welcome, Lorna.
-
4.21 on my Laptop (Windows 10) the location is incorrectly showing Europe Asia even though the LAT/LON it's showing is actually the North of England.
I know we're going through Brexit and everything but I don't recall England becoming part of Asia ;-)
-
@dragon2611 Wow, ok (also thanks for the giggle). Can you message me your coordinates or send a screenshot? Does Google maps locate you correctly?
-
Since this new update and turning the "Use Monitor Data for Calibration" ON in whatever setting i use (2700k 3400k etc) its more yellowish, it will take time to get used to it. So I assume that it due to my laptop screen calbration....
-
@sitayi2308 maybe we should make a visualizer for it :) which laptop do you have?
-
-
@herf A humble ASUS X555L
-
Fixed another color bug, sorry!
https://justgetflux.com/flux-setup4-23.exe -
@lorna Right, it's just difficult to reach f.lux while the window is still active if it's fullscreened, because bringing up the taskbar to get to f.lux deactivates the window in question.
A totally separate thing to note is that f.lux also seems to be creating multiple entries in the "hide/show taskbar icons" settings, depending on what time it is. So my list contains items like:
- f.lux
Sunset: 4 hours ago, Wake in 9 hours - f.lux
Sunset in 43 minutes, Wake: 11 hours ago - f.lux
Sunset in 13 minutes, Wake: 11 hours ago - f.lux
Sunrise in 5 hours, Wake in 7 hours
which are continuously appearing, and must all be turned on/off in order to consistently show/hide f.lux in the taskbar, else it will appear and disappear as time passes.
- f.lux
