f.lux beta (another thread)
@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:
Sunset: 4 hours ago, Wake in 9 hours
Sunset in 43 minutes, Wake: 11 hours ago
Sunset in 13 minutes, Wake: 11 hours ago
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.
TwoCables last edited by TwoCables
I'd like to see the ability to use the color-changing keyboard shortcut to go back to 6500K from 800K. Right now, I can get close but it's either 6300K or 6550K.
Transitions while the f.lux window is closed are very choppy for me. When the window is open, they're fairly smooth.
I think that radio buttons should be used on menu items that can't be deselected when clicking them again. Check marks make it feel like I can just click the currently-selected item to deselect it.
When I have f.lux disabled for a specific program, or for an hour, or until sunrise, I think it would be nice if it would say so in the window instead of just "Disabled".
If I'm using custom colors and I go and select a different preset like "Recommended Colors" or something, I would love the ability to instantly go back to my Custom Colors by having a menu item by that name to choose from in the drop-down menu.
I'm not sure if it's supposed to be automatically updating, but it's not.
The download link in the beta thread (https://forum.justgetflux.com/topic/3675/f-lux-beta-for-windows) isn't for 4.23 either.
I found a weird bug. Here's how to reproduce it:
- Put f.lux in Bedtime mode
- Choose a color that's warmer than 6500K for either Daytime or Nighttime, depending on the underlying mode that f.lux is in.
- Hold down CTRL and try to get Bedtime mode to be in 6500K.
What you should find is, you can only go as high as 6450K. As soon as you put the slider in the 6500K position, the set color temperature drops down to the warmer color for Daytime or Nighttime that you chose, but the slider stays in the 6500K position. It only does this for Bedtime mode. If you release the slider button by releasing your mouse button, the color temperature will drop down as depicted.
I think it would be nice to choose how long the f.lux window stays open for when it's not in focus.
I think Movie Mode should be forced on if you choose it while your current color temperature is higher than 4400K.
I might have more to post later.
Posting 4.24 which avoids interrupting fullscreen apps with notifiers and popups, so at least we can use hotkeys to debug these cases.
I found that having the monitor data for color calibration ON, (im using 2700k) the screen is yellowish....i dont like very much, so if i disable it it goes to f.lux default color right?
TwoCables last edited by
2700K is supposed to be yellowish.
@sitayi2308 yes it goes back to the old code instead
@TwoCables Actually it was more red...but i will get used to it. BTW, nice job Herf and Lorna.
4.24 still thinks I'm in Europe, Asia same as screenshot posted earlier for 4.21
@dragon2611 We are using the windows location service. Can you run the "Maps" app from Windows and see if it is doing the same thing?
@herf it's correct in there as far as I can tell (it only shows the Lat/Lon when I enter that) it's also correct on the Map in Flux it's just the text under the location box that's wrong.
55.00N, 1.60W is an area near Newcastle Upon Tyne not really sure why that gets set when I did give it my actual postcode, but anyway it's close enough for the purposes of calculating the sunrise/sunset.
Where Flux is picking up the (Europe, Asia) text from though I'm not sure
Sorry, I understand the issue now. We are trying to show your continent to avoid people pasting in "E" when they mean "W" and so on. Back before we had the map this was a common problem. Of course with the map there, it is sort of redundant.
I can imagine that someone in the UK would not think of "nearest continent: Europe" when they see "Europe".
@herf Ah it's unclear that it means that,
Ah Now I understand, I think perhaps the UI could be a bit clearer in alerting a user it won't necessarily store their precise location so they don't get confused when they go back in next time and see something different to what they entered.
Please add brightness to the color settings.
Could use a disable/set color/brightness per app. (this would be amazing!)
Bug: The task tray icon forces itself back to being "shown" after each PC reboot. I like to keep my taskbar minimal and clean, so this is making me have to drag it back up to the hidden tray every time I start Windows. (Windows 10)
Tungsten_smooth last edited by Tungsten_smooth
Bug report: "The sun is up. Light is making your body later". I also suggest to rephrase this to similar: "light is making you wake later". Also, the slider is showing the position of the daytime color selection, so not sure what it should show there--maybe the current color, updating every 20 minutes?
@phrontisteries yes we have brightness schedules in our internal build, but it is complex enough that we have not shipped it yet.
Actually, a couple years ago, I had my screen on a "forced" schedule, so f.lux was controlling the dimmer exactly. This was pretty good, but occasionally very frustrating, because when it was wrong, it was awful.
Since then, we've tried to listen to the keyboard keys that adjust brightness, so you can override our "forced" schedule. This almost works, but there is enough 'noise' in the system (power changes, ambient light sensors, etc.) that it wasn't ready for prime time yet.
That said, I really wanted to get it done for this version, so it is still on my list for the next one.
@Tungsten_smooth yes we have more to do here. Wake time corresponds somewhat to circadian time, but not exactly - it is also related to sleep debt and the ability of the body to stay asleep (which varies by age). So if you talk to elderly people who have trouble sleeping through the night, they often need a stronger "amplitude" signal (more light during the day) and not always a "phase shift" in schedule (as do 20 year old students who have to get up early for class).
For f.lux right now, it is a very important time to show "how your body is reacting". This next chapter is "how to help your body do what you want it to" and I hope that can be simple too.
In the UI, the big slider should usually reflect the current-nearest preset, which is not the best way to do it, but better than having an infinite number of control points that are hard to delete! We could do this better but it makes sense at most times of day.
I'm on 4.21 and it doesn't play nice with Windows 10 (toast) notifications. As there is no option in the program's menus, I switch off the sound or even the notification altogether in WIndows Settings (screenshot attached), but after a system restart, f.lux resets the notifications, creating a new entry in the notifications app list.
As if f.lux is registering a new instance with the notification system each time. Kind of annoying. I'd love in-program options or a fix for playing nice with Windows system.
Otherwise I love what you did with per-app options. Been waiting for it for ages.
I have both f.lux 4.21 on my Windows PC and f.lux 39.94 on my MacBook Air next to each other.
The location is the same and on Windows I have set the transition time to "slow" and on the Mac I have disabled the "fast transitions" option.
Unfortunately their timing is not the same. :cry:
f.lux 4.21 on Windows is already at 1900K while Mac with 39.94 is still at 27xxK and still going down.
Can you please align the transition times across these platforms? Bonus points if the Android app also does exactly the same. :)
@hsiktas well they are using the same code, finally. Things to check:
- same wake time
- same location
- same presets
- https://justgetflux.com/timesync.html looks similar?
It turns out my Mac and PC are about 8 kelvin apart (testing during the fastest portion of the bedtime transition), but they are also about 7 seconds apart too.
The next update may shift the wake timing a bit, so there might be some skew until we update the Mac. But right at this minute for you, they should be the same.