home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
HTPC Projects
Software
Operating System
Windows 7 & half fullscreen
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Scythe42" data-source="post: 952394" data-attributes="member: 95833"><p>Whenever a monitor is disconnected by whatever event, specs require a reset to 1024x768 XGA resolution. This of course affects any open windows on the desktop. MP runs in a borderless window. Not a real full screen!</p><p> </p><p>Depending on your GPU it might not reset the resolution to 1024x768. In fact mine system does not not. It changes the resolution to 1920x1200. Never changed anything in the registry. And because the resolution is larger, I never suffer this effect. It seems that this is the same way for all systems that are fully compliant to the latest ACPI level and all legacy crap in BIOS/EFI is turned off. They never go to the old windows 1024x768 default resolution but instead to the maximum supported resolution per connected display (1920x1200 in my case).</p><p> </p><p>These systems will see an ACPI HOTPLUG event as a Windows message as well.</p><p> </p><p>Anyway the 1024x768 fallback is fine. MS changed this a bit in with Win8. Most people should not experience this issue in Win 8 (of course depending on the GPU driver as usual). MS changed a lot in regards to screen resolutions as they also intended to run Metro on one screen and desktop on a second screen. For this they adjusted a lot. To be honest with Win8 Multi Displays Support is finally on par with OSX. </p><p> </p><p>Currently fine-tuning the patch in Area 51 by testing it out on various systems until we find a solution that works for everyone.</p><p> </p><p>This large patch (reworking a lot of related D3D features) will make MP aware of size changes in fullscreen and automatically adjust to the new resolution and stopping any events that cannot be done during resolution changes (e.g. movie playback). </p><p> </p><p>When a window is larger then the resolution Windows makes it smaller. But it doesn't make it bigger again later automatically. So we need to teach MP to resize itself to the full resolution automatically when running in fullscreen and at the same time preventing the D3D device to hang if the resolution becomes to small for the current window size.</p><p> </p><p>Any application has the same problem when it cannot handle resolution changes. Applies to XBMC as well. XMBC simply minimizes itself to the tray on a resolution change by Windows and requires manually reactivation. This already works for MP with the current patch. But I want to bring MP automatically back to the front.</p></blockquote><p></p>
[QUOTE="Scythe42, post: 952394, member: 95833"] Whenever a monitor is disconnected by whatever event, specs require a reset to 1024x768 XGA resolution. This of course affects any open windows on the desktop. MP runs in a borderless window. Not a real full screen! Depending on your GPU it might not reset the resolution to 1024x768. In fact mine system does not not. It changes the resolution to 1920x1200. Never changed anything in the registry. And because the resolution is larger, I never suffer this effect. It seems that this is the same way for all systems that are fully compliant to the latest ACPI level and all legacy crap in BIOS/EFI is turned off. They never go to the old windows 1024x768 default resolution but instead to the maximum supported resolution per connected display (1920x1200 in my case). These systems will see an ACPI HOTPLUG event as a Windows message as well. Anyway the 1024x768 fallback is fine. MS changed this a bit in with Win8. Most people should not experience this issue in Win 8 (of course depending on the GPU driver as usual). MS changed a lot in regards to screen resolutions as they also intended to run Metro on one screen and desktop on a second screen. For this they adjusted a lot. To be honest with Win8 Multi Displays Support is finally on par with OSX. Currently fine-tuning the patch in Area 51 by testing it out on various systems until we find a solution that works for everyone. This large patch (reworking a lot of related D3D features) will make MP aware of size changes in fullscreen and automatically adjust to the new resolution and stopping any events that cannot be done during resolution changes (e.g. movie playback). When a window is larger then the resolution Windows makes it smaller. But it doesn't make it bigger again later automatically. So we need to teach MP to resize itself to the full resolution automatically when running in fullscreen and at the same time preventing the D3D device to hang if the resolution becomes to small for the current window size. Any application has the same problem when it cannot handle resolution changes. Applies to XBMC as well. XMBC simply minimizes itself to the tray on a resolution change by Windows and requires manually reactivation. This already works for MP with the current patch. But I want to bring MP automatically back to the front. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
HTPC Projects
Software
Operating System
Windows 7 & half fullscreen
Contact us
RSS
Top
Bottom