Special
120 discussion posts
Why was this changed? Is this suppose to happen now or a bug, it never was the case before.
Dec 19, 2018 (modified Dec 19, 2018)
•
#1
Special
120 discussion posts
Does it have something to do with this?
"Fix: Apps launched from the DisplayFusion taskbar now get the correct environment variables"
Definitely not intentional! I will test tonight and we'll get it fixed up for the next beta.
Thanks!
I can't reproduce this here. Could you attach a copy of your troubleshooting info?
Also, do you just use the built-in Windows Task Manager, or have it replaced by something else (e.g. Process Explorer?)
Special
120 discussion posts
I use the built in Task Manager, you can even see the process "DisplayFustionSettings.exe" briefly when TM opens then the process closes after a few seconds.
Edit: I just want to add it only happens when launching TM by right-click on the DF's Taskbar.
---
Also unrelated, but in the change log what are these new options you speak of? "Change: New advanced settings"
Dec 20, 2018 (modified Dec 20, 2018)
•
#5
The brief launch of DisplayFusionSettings.exe is expected, we made it do that so that it gets the latest environment variables (because the existing DisplayFusion.exe process doesn't). The new DisplayFusionSettings.exe process starts, then launches the app shortcut (or Task Manager in this case).
Is the DisplayFusion Settings window actually openeing, or does Task Manager ultimately launch?
That change log item refers to the Settings > Advanced Settings window, just a few new options added there for making small tweaks on some machines.
Special
120 discussion posts
The settings windows does not launch, it's only the process of it that runs, TM opens just fine, I was only wondering if this was expected behavior because it was not so in the past (v9.4 Beta 5) was the last one I was on for v9.4, but if you say it's the new behavior then I guess it's no bug.
