Yannis Rivard-Mulrooney
4 discussion posts
Hello, I noticed a bug in the feature to send scroll commands to an unfocused window currently under the mouse cursor. When on any monitor, if you click on the desktop and then try to scroll on an unfocused window it simply does not work. My guess would be that you guys check if the mouse is in the area occupied by the current window before checking the window under the cursor, and in the case of the desktop, it covers the whole screen area even if it is in the background. I'm using the latest version (5.1.1) of displayfusion on windows 7.
I've tested this out here in Windows 7 x64, but it seems to work fine. Are you on Windows 7 x64, or x86? Also, does it occur with specific applications only? I tested it out with Internet Explorer 11.
Thanks!
Yannis Rivard-Mulrooney
4 discussion posts
Strangely enough I can't seem to reproduce the problem now... At the time of writing it occurred every time I tried, and I was testing with Chrome. I am running Windows 7 x64.
EDIT : I just restarted my computer to see if it would have an effect, and sure enough the described behavior started happening again. I have 2 Google Chrome windows opened (one on each of my monitors). When I minimize one and click on the desktop, I can't scroll on the other one. If I focus any of the two windows, the scrolling works fine on both. I tested with Steam too and the same thing happens, so I don't think this is specific to Chrome.
I attached a log file (logging set to detailed) of some scrolling in case it might give you some info on the problem.
• Attachment [protected]: DisplayFusion.log [225,874 bytes]
Jan 20, 2014 (modified Jan 20, 2014)
•
#3
Yannis Rivard-Mulrooney
4 discussion posts
Just wanted to mention that for some reason, the problem stops when I change my wallpaper. I reverted to the wallpaper I was using at the time when the problem occurred and the problem did not come back either.
Interesting! I'll test this out again to see what I can find.
Well that's definitely interesting! I was able to reproduce the exact behaviour you're seeing. I've added this to our list, and we'll be sure to let you know when we've gotten it sorted out.
Thanks!
Yannis Rivard-Mulrooney
4 discussion posts
Great, glad I could help with finding this bug!