Stefan N.
50 discussion posts
Hello,
I'm using DF for some time now and since today, I have an Eyefinity setup. DF offers the function to virtually divide the desktop back into the three original parts which is a killer feature in my opinion as it enables me to use maximize windows on different monitors which would not be possible otherwise!
But there is one issue which makes the feature less good: obviously, the bezel correction is not taken into account correctly when calculating the virtual monitors. This causes the virtual screen resolutions to be larger than the screen itself and on the sides, the content is "cut off" as it lies in the invisible (bezel) area between the screens.
Another problem is that DF does not "remember" if you have positioned a window on a certain virtual screen. If I e. g. start Paint.NRET, it always opens maximized over all three windows. If I then move it to the center, maximize it on the center and close it, the next time it again starts spanned over all 3 screens.
Are you aware of these issues? Are you planning to fix this soon? This would make DF the best solution to handle Eyefinity setups!
Best regards
Stefan
• Attachment [protected]: P1100842.JPG [63,093 bytes]
• Attachment [protected]: P1100843.JPG [66,594 bytes]
Stefan N.
50 discussion posts
Can you perhaps give some more info about the problem with this feature? Wouldn't it be sufficient to substract the original resolution (5760 x 1080) from the bezel resolution (in my case 5940 x 1080) to get the info how many pixels are used for the bezel correction? In my case this are 180 pixels, so each bezel has 90px. And these 90 pixels now need to be added taken into account when calculating the splitting information used for creating the "virtual" desktops?
Unfortunately it's not quite that simple, as the monitor splitting feature is designed for more configurations than just Eyefinity/Surround. For example, you can split monitors that aren't part of an Eyefinity/Surround group, or you could split an Eyefinity/Surround group into unequal parts (i.e. 7 splits on a 3 monitor group). It's all of those kind of weird scenarios that make it difficult, and we just need to make sure we can spend the time and get it right for every possible scenario.
Rest assured that this is still planned, and we'll post an update when we break some ground on it.
Thanks!
Charles David Gibson
1 discussion post
How is this coming? We need this for displayfusion to shine.
Stefan N.
50 discussion posts
Hi Keith,
also works good for me so far, however while testing the possibility to move around windows between the screens, I found two issues when working with maximized windows (before I only worked with non maximized windows by resizing and moving them around with shortcuts).
If I maximize "eM Client v6.0.21040" and "iTunes v12.0.1.26", they look really bad and the position is also not valid.
For iTunes, the maximized window is not located properly. top, so the actual upper left position is outside the visible desktop area (see attached screenshot, non-maximized vs. maximized).
eM Client also looks strange, I also attached a screenshot for this. It looks fine when windowed, but also here parts of the window are located outside the visible area when maximized.
Hope it is a generic root cause so that I do not have to test every installed program ^^ OS is Win 7 x64.
Best regards
Stefan
• Attachment [protected]: emclient.png [5,593 bytes]
• Attachment [protected]: itunes.png [14,748 bytes]
Stefan N.
50 discussion posts
Hi Keith,
thanks for the update. Maybe I will start a request at the developer why they are not using the default behavior here and let you know...
The described behaviour s the same for iTunes and eM Client, isn't it? This then means iTunes is also not using the default window maximize funcrtion?
Best regards
Stefan
It's a bit more complicated than what I described, and I can't offer more details (I'm not a developer myself), but if the eM Client devs have any questions for us, please have them send them to us at support@displayfusion.com and I'll relay them on to our devs.
Thanks!