f.lux beta (another thread)
-
@herf said in f.lux beta (another thread):
Mouse fix is rolling out as 4.27 - sorry I just broke the checkbox.
hehehe good job. :)
-
@herf Thank you for your work! F.lux is really amazing piece of software, must have!
I am looking for other improvements and features, keep us updating.
P.S. Would be nice to add a link to your website for changelogs/post changelogs for every version here on forum in one thread.
-
@herf can you please explain what exactly Software mouse cursor (fixes "white cursor") does in these last builds?
-
The new build seems to have fixed my calibration issues. I'm not sure how, but thanks.
-
v4.27 - I like the new way how you redesigned the f.lux settings - much better!
My ideas:
- make the setting icon under the day preview easier to open - some users dont know that it is settings
- add a link to change location to this menu (mentioned above)
- settings for disable - I think that name of apps is not complete (only one word from the first name; should you capital letter)
- on mouse hover (icon next to the clock) - show color temperature
Just my ideas, sorry for my English, not my native language.
-
I think there should be a way to manually choose a program when configuring autodisable settings. Having to start the program and have it selected is kind of a pain and not always practical.
Also, for some reason f.lux un-hides itself from the system tray at start. That's kind of annoying. -
@KZcheese said in f.lux beta (another thread):
I think there should be a way to manually choose a program when configuring autodisable settings. Having to start the program and have it selected is kind of a pain and not always practical.
I agree!
-
BTW shouldn't there be an option to stop f.lux from running at startup? I know the point is to integrate the program seamlessly with windows but an option would still be nice.
-
So Windows has these Notification Area Icon settings where you can change stuff on a per app basis, since flux changes path to the exe on every update (assumed) it counts as a new app for those settings and falls back to the default.
Can this be avoided? I suggested using Squirrel (https://github.com/Squirrel/) as an updater before, it avoids this by pointing to a stub exe which never changes path/version but if you don't want to use Squirrel, the same technique could be applied here, too.
-
@opensan said in f.lux beta (another thread):
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.
Oh this is the same problem I just reported, sorry for duping. It's because of the path of the exe changes with every update
-
Oh also, an option to not popup the changelog on every update? It's like a scare jump for me :)
-
It's still broken.
-
@KZcheese said in f.lux beta (another thread):
BTW shouldn't there be an option to stop f.lux from running at startup? I know the point is to integrate the program seamlessly with windows but an option would still be nice.
This.
I am always disabling it on every single update by deleting this Registry subkey:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run f.lux* (it's in the right-hand pane)
I don't need it or want it starting with Windows.
-
@TwoCables I usually disable it in the Windows 10 Task Manager or CCleaner when I need to. I find that much easier.
-
@KZcheese said in f.lux beta (another thread):
@TwoCables I usually disable it in the Windows 10 Task Manager or CCleaner when I need to. I find that much easier.
I have Windows 7, so I have to delete that Registry sub key. I refuse to use CCleaner for any reason as well.
For me, getting it out of the Registry is super fast because I have that main key as one of my Registry 'Favorites' (among others). It's a 'Run' key, and so it's useful for more than just stopping f.lux from starting with Windows.
-
Yeah that's another issue caused by the installer
-
@Stanzilla said in f.lux beta (another thread):
Yeah that's another issue caused by the installer
??
I have no issues caused by the installer.
-
Also, I was using 4.25 when 4.27 was pushed out and I had my automatic updating turned off. Yet, I still got the "f.lux is updating" page even though f.lux didn't update (until I decided to allow it to update).
-
@TwoCables said in f.lux beta (another thread):
@Stanzilla said in f.lux beta (another thread):
Yeah that's another issue caused by the installer
??
I have no issues caused by the installer.
If the installer has no option to not set the reg key then yes, it is
-
@Stanzilla said in f.lux beta (another thread):
@TwoCables said in f.lux beta (another thread):
@Stanzilla said in f.lux beta (another thread):
Yeah that's another issue caused by the installer
??
I have no issues caused by the installer.
If the installer has no option to not set the reg key then yes, it is
We were talking about having the option be in the UI. We just need a simple option in the UI to choose whether f.lux starts with Windows. That way, the installer can stay simple and those who shouldn't be messing with this won't be enticed to.
