Smeeta
1 discussion post
After upgrading from an older DisplayFusion version (9.x or 10.x not really sure) to 12.1.1, scripted-function hotkeys have approximately a 2-second delay on the first activation. Subsequent usages are immediately.
The delay doesn't happen every single time, but is particularly noticeable after DisplayFusion has been idle/restarted.
The script is a simple application mute while focused function (even from the script section on this website):
BFS.Application.GetAppIDByWindow() followed by BFS.Audio.GetApplicationMute() and BFS.Audio.SetApplicationMute().
I also tested disabling "New Assembly Resolver" in advanced settings, but this does not change the behavior.
Windows 10
Displayfusion 12.1.1
That's very strange, I haven't heard of anyone reporting this before. Let me look more into it and get back to you.
We have a new beta scheduled for next week and I'm interested to see if the performance improvements will help this issue. I'll follow-up once it's available to test. Thanks!
G.T.
8 discussion posts
I’m experiencing a very similar issue with DisplayFusion triggers.
After DisplayFusion has been idle for a while, the first trigger activation is delayed by several seconds. Once it finally executes, subsequent activations work immediately. After another period of inactivity, the delay returns again.
This used to work perfectly without any noticeable delay in older versions of DisplayFusion.
