justpoo
18 discussion posts
I have three identical 2048 x 1152 monitors and run Windows 7 with a DPI scale of 200%. The problem is with any full screen app, like flash player, or apps like Windows 7 Manager or KMPlayer - when I use "move to next monitor" they shift twice as far as they should, sometimes completely offscreen as to make them difficult to retrieve. So an app that's on monitor 1 will shift right to monitor 3, to a phantom monitor 5, then to 1 again. Programs like Firefox or Thunderbird or Explorer aren't affected. When I had the DPI setting at 175% the apps moved 1.75 screens a time etc.
If I use "XP scaling" when choosing the DPI setting of 200% then there's no problem with DisplayFusion, but then I can't see my programs properly. The only way to make them big enough and consistent with my other unaffected programs is to deselect XP scaling.
If you could help me out with this it would be very much appreciated!
Apr 4, 2012 (modified Apr 4, 2012)
•
#1
Interesting! Thanks for posting the steps to reproduce. I'll do some testing with this and we'll see what we can figure out.
Thanks!
justpoo
18 discussion posts
An easy way to find affected programs - just look for any that have a "skinned" GUI. So in addition to the ones I mentioned, CCleaner, MediaMonkey, Comodo Internet Security, Logitech Setpoint, 7Zip and Creative Console Launcher also display the behaviour. Obviously you guys will know what the commonalities are under the hood, are the interfaces all flash or java based? Or something?! I'll leave it in your capables, that's the limit of my techspertise!
Ok, good to know, thanks!
justpoo
18 discussion posts
Thanks for fixing this, it's behaving much better now. Bit odd with some apps but I'm not complaining - I can see what I'm doing now! Thanks again, top job.
justpoo
18 discussion posts
Just one thing, I use Miranda for IM and I think this fix for the DPI has unintentionally broken part of it. When you click on the wee system tray icon it should pop up the contact list, it no longer does so. It used to pop up right next to the taskbar I'd clicked, but now it appears in a random place and only for a second, or not at all. I'll use something else in the meantime, have a nice weekend.
justpoo
18 discussion posts
Rolling back fixes the issue, seems to be a new problem. I use Winpopup and RealReconnect, that's about it. I'm running it at 165% DPI at the moment, flicking a DPI-affected program like DFX or Setpoint is a bit weird as it not only will open offscreen if i click a DF taskbar(aligned far left or right) on the right or left screen, when i then right click the taskbar button and manually shift to next monitor it seems to move pretty randomly, both horizontally and vertically. Sometimes it'll shift one screen, a screen and a half, sometimes it'll shift a few pixels right and then 500px up, or, and I think this is what's happening with the miranda contact list, it shifts downwards and offscreen. I'm not sure if I've made your life easier or harder with that, but there you have it!
Interesting... do you have the "Use Windows XP style scaling" option enabled or disabled?
justpoo
18 discussion posts
It's disabled, if I enable it then everything is normal, but the apps don't scale at all
Ok, good to know. DFX is busted in Beta 15 and 16 for me, but Miranda IM seems to work fine in both Beta 15 and 16. Is your Miranda IM windows skinned at all?
justpoo
18 discussion posts
That's a good point - it is, but I can't find what it is as I have been backing it up so long I just copy paste the files to the new installation, I think midnight glass from memory?! I think it needed the gtk kit wotsit
Apr 30, 2012 (modified Apr 30, 2012)
•
#12
Would you be able to send me a copy of the files so that I can test the same setup as yours? Or would that include your account info too?
justpoo
18 discussion posts
I'll attach some old files for you, they use the same settings but the user account is seldom used so just delete after you're done (still, don't go msging anyone!)
Thanks! It doesn't seem to be skinned, but it didn't have your account info either, so maybe there's some additional configuration needed.
Anyways, I was able to reproduce the issue with DFX, so we'll see if we can sort that out. If not, we may need to revert the changes that we made to fix your original issue for now.
Just a quick update: We've hopefully gotten the issues with Miranda IM and DFX sorted out. Could you give 4.0 Beta 17 a try when you have a chance?
Thanks!
justpoo
18 discussion posts
It has sorted DFX and Creative Control Launcher, but Miranda still seems to be the same. I noticed a funny behaviour with full screen flash, it's much better than it was but it doesn't quite align when you swtich monitors, it is maybe 50 px off. If i open Setpoint in the right window then it is offscreen, one I bring it back on it behaves normally. I've attached a screen shot, you can see the miranda window at the bottom of the middle screen, if I flick it to another screen then it becomes visible, but once I click the wee system tray icon to open it in another monitor it goes back to off screen again.
• Attachment [protected]: Untitled.png [6,927,560 bytes]
justpoo
18 discussion posts
Sorry, you're absolutely right, it is broken in 15. When I tested it before I was right clicking the Miranda icon and selecting Hide/Show to make it appear - if I left click the icon it doesn't appear anywhere, not even at the bottom and there's no way to find it.
Just a quick update, we've been super busy here, and I haven't had a chance to really get back to testing the other issues with DPI scaling. I'd still like to test and work on these, hopefully in a couple of weeks.
I know you were having trouble with Miranda IM with the custom skin. Are there any other applications that you're still having issues with that I should test out?
Thanks!
justpoo
18 discussion posts
Well I've been using it on 150% of late and most problems seem to be OK now. At 165% there's problems with almost all of the programs I listed, strange behaviour when switching screens or using DF to open programs to a particular monitor. Logitch Setpoint is a good example of this, if you click the system tray icon to open it then the program momentarily appears on the centre (my main display) and then disappears somewhere offscreen. I recently changed my graphics card from nvidia to amd and there's a whole host of issues with Eyefinity and DF, but I did a search in the forum and saw that it would take a considerable rewrite of your code to begin to address these, so the DPI issues we're talking about refer only to those discovered in three display mode.
Ok, great to know. I'll check out the 165% scaling issues in a couple of weeks and I'll let you know what I find out.
As for Eyefinity, we are planning to add some better support for it at some point, just can't provide a timeline at the moment.
Thanks!
justpoo
18 discussion posts
A problem I noticed today - if an open Trillian window is a few inches to the right of the cursor, then the mouse will not scroll the window or app it's over, I think it's detecting the Trillian window as being underneath. Also, when you grab a Trillian chat window to move it, it doesn't grab it where the cursor is, it grabs it a few inches to the left of the window. Just noticed it and though you'd like to know.
Just wanted to follow-up with you to see if you're still using a DPI setting of 165%, and if so, are you still running into issues with certain applications?
Thanks!
justpoo
18 discussion posts
No I've stuck to 150% and increased the fonts a little, no real issues at all. In fact the only issue I have is the occasional crash when using flash in fullscreen, DF CPU usage stays at a steady 13% and has to be force quit. Oh, while I have you, is there an option to always keep DF taskbars in front of fullscreen apps? I have a feeling it's already a feature but I can't find it.
justpoo
18 discussion posts
I couldn't tell you exactly but it's been happening for a couple of months, i keep up to date with the betas. Thanks for the fullscreen tip, much obliged!
No problem! Let me know if the crashing issue still persists after you've changed the full screen setting. Perhaps it's related to some full screen detection that we're doing.
Thanks!