gzusphish
4 discussion posts
This is an odd bug, but I've noticed that when DF is running and I right-click on a non-text file the mouse suddenly stops displaying correctly. The mouse doesn't slow down but it's refresh interval is set to about once per second. So if you move your mouse across the screen in one second then it will appear to say still until the second passes and then it will appear on the other side of the screen. It's the same for all motions; they appear in steps with a one second refresh rate.
I'm positive that it's DF that's causing this because I turned off programs until the mouse's behavior returned to normal. Now when I turn DF on the mouse screws up and when I turn it off the mouse acts properly. I also noticed that when DF is running the abnormal behavior of the mouse is only confined to context menus for files that are not plain text formats (i.e. pdf, jpg, exe, zip, etcetera...).
FYI: I'm running XP Pro SP2 on an IBM T43 and DF Basic version 2.0.2.
Thanks in advance for your help.
Kevin F.
456 discussion posts
I noticed that as well, but blamed it on windows being..... itself. I almost have the same situation.. Context menus come up after a few seconds..... Just tested and it sadly was DF........
I haven't been able to replicate this issue so far, could you explain it a little bit more for me? When you right-click on the file, is this a file on the Desktop, or in Windows Explorer, or does it happen anywhere? What video drivers do you have installed (are they Intel ones)? It is very strange that this behaviour is limited to non-text files.
Can you try going into the Settings and disable the settings called "Enable maximized window dragging between monitors"? Let me know if that changes anything, or helps it at all.
Thanks!
gzusphish
4 discussion posts
I tried disabling the "Enable maximized window dragging between monitors" setting as you suggested and the problem appears to have subsided. It's too bad, though, because that was one of my favorite features of DF.
On the subject of the issue; first a little sysinfo:
IBM T43 laptop Type 2678-A44
MS Windows XP Pro v.2002 SP2
Display adapter: ATI Mobility Radeon X300
Display driver version: 8.163.1.11 dated 1/21/2006
I'm using a dual-monitor setup in a vertical arrangement. The upper monitor is an LCD and the lower - and primary - is the laptop's display. (BTW can you recommend a site where I can get backgrounds for a vertical setup?)
I ran some additional tests and determined that the issue is not limited to any particular group of files and it doesn't occur 100% of the time. It is, however, limited to Windows Explorer and doesn't appear to affect the desktop. It also affects the context menu when you right-click the white background in the window but still not 100% of the time. On average it seems to occur for about 80% of context menus in Windows Explorer.
Also, if I pull up context menus on the same file repeatedly, without clicking anything else, then the first context menu will cause the mouse frame-rate to drop but all future context menus - as far as I can tell - will function normally.
Finally, if I turn off the "Enable maximized window dragging between monitors" setting the problem disappears and stays gone even if I re-enable the setting, although the setting will remain non-functional until I restart DF. But if I re-enable the setting and restart DF then the problem returns.
Just for clarification - and this may be unimportant - the mouse's movement distance is unchanged by the problem; its only the render time that changes. The mouse appears to jump from place to place but never disappears entirely.
Yesterday I released the new DisplayFusion v2.1, and the mouse hook code was almost completely rewritten and should be much more efficient now. If you are still interested in trying DisplayFusion I would be interested to hear if you are still experiencing this issue.
Thanks,
Jon
gzusphish
4 discussion posts
w00t...it worked. My mouse is moving at full speed now and context menus are even opening faster. NICE.
Samw: Give DisplayFusion v2.2 a try - it should address this issue.