
liuhui0803
2 discussion posts
DisplayFusion v 2.2.116 Beta 16 has an UI layout problem in Settings window.
In "Window Snapping" tab, the "Window Snap Distance (Pixels)" text is too low (see Snap1.png). I have tried English and Chinese UI, both have the same problem.
And another problem is about checking update function. If DisplayFusion is set to srart with Windows, sometimes when I restart computer and login, DisplayFunsion will checking update automatically, but if system is not fully started yet, or is still trying to connect to Internet, the checking operation will fail and display an error message. So I suggest to set a delay time here, and only when DisplayFusion have started, only past the delay time, then it could checking update

Snap1.png
I think it might be the font you're using - on my machine it is a 'bit' low but not causing the overlap with the integer selection box like in your pic:
I am I.

DF v2.2.116 Settings.PNG

liuhui0803
2 discussion posts
I think 60 sec delay would be better, cause some machine has lots of sutff to load when starting, this maybe make Internet connection a little slow, and updating of DisplayFusion is not as important as update Windows or other security app. So I think a more longer delay could be acceptable.
The font problem, I don't know why, but if there has anything need me to do, please let me know
Would it be easier to implement a delay in the launch of DF itself? We all know that at startup our machines are going crazy with all sorts of apps trying to start up on their own - things like IM clients, AV / AM software, FWs, all pertinent services, and a whole slew of other things....
I know that with WinPatrol I am able to designate wait times in Vista / W7 natively, but I have also heard that it is possible in XP via WinPatrol or other 3rd party apps....
I am I.
There should be a way to implement it - both Vista and now W7 (I presume) have that feature built in, unless that is reserved for services only?
As for XP, of course that would require a third party application....
I am I.
lol I noticed that in the changelog but kept my mouth shut....
I am I.
But you had already corrected he error - where it counts, in the code.
At that point it was moot to me....
I am I.