http://bugs.winehq.org/show_bug.cgi?id=34613
Bug #: 34613 Summary: Hot Corners are active when using programs in fullscreen mode (the mac driver) Product: Wine Version: 1.7.3 Platform: x86 OS/Version: Mac OS X Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: winebugs140@gmail.com Classification: Unclassified
When you use a program/game in fullscreen mode, resolution of which is the same as that of your desktop, Hot Corners are active (of course, if they are turned on in system settings). It can be especially annoying if one needs to point things with the mouse cursor in such a program. Also, after activating a Hot Corner the application loses the focus, then you can see, for example, two mouse pointers.
Although it would be rather unusual to leave such a Hot Corner function as "Sleep Display" working in fullscreen mode, for example in Team Fortress 2 (with the native Mac Steam client) you may open Dashboard with hot corners which is then displayed over the game. It has to be decided whether turn off all Hot Corner functions in fullscreen mode with the mac driver or just some.
Not a problem with the X11 driver.
http://bugs.winehq.org/show_bug.cgi?id=34613
WineBuG winebugs140@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ken@codeweavers.com
http://bugs.winehq.org/show_bug.cgi?id=34613
Ken Thomases ken@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #1 from Ken Thomases ken@codeweavers.com 2013-09-28 06:58:25 CDT --- A program doesn't have any direct control over whether hot corners are enabled or disabled. The only control we have is whether we capture the display or not. If we capture the display, then things like the volume indicator, battery indicator, and system alerts can't show. Functionality like three-finger swipe to change spaces is disabled. Command-Tab doesn't work as normal, although the Mac driver tries to do something sensible. And, also, the hot corners are disabled. This is what happens if you use a resolution other than the normal desktop resolution because we have no choice but to capture the display in that case.
So, it's something of a trade-off.
I have considered adding a registry setting to control it, but haven't done so yet.
http://bugs.winehq.org/show_bug.cgi?id=34613
--- Comment #2 from Ken Thomases ken@codeweavers.com 2013-10-01 20:01:46 CDT --- Actually, I did add a registry setting. I just completely forgot!
I just added the explanation of the CaptureDisplaysForFullscreen setting to the http://wiki.winehq.org/UsefulRegistryKeys page. If you set that to "y", then the Mac driver will capture the displays and that will disable hot corners.
http://bugs.winehq.org/show_bug.cgi?id=34613
Ken Thomases ken@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID
--- Comment #3 from Ken Thomases ken@codeweavers.com 2013-11-27 10:03:56 CST --- Marking invalid because the fix was already present before this was filed.
http://bugs.winehq.org/show_bug.cgi?id=34613
--- Comment #4 from Bruno Jesus 00cpxxx@gmail.com 2013-11-27 12:50:59 CST --- (In reply to comment #3)
Marking invalid because the fix was already present before this was filed.
But there was not bug related to it so IMO I think it's fine to leave this as fixed with commit 220b8b7946397b7605e53d97c8b0d3aafe55d4d5. We have done this before, I just can't find an example now :)
http://bugs.winehq.org/show_bug.cgi?id=34613
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |FIXED
--- Comment #5 from Austin English austinenglish@gmail.com 2013-12-02 14:41:09 CST --- (In reply to comment #4)
(In reply to comment #3)
Marking invalid because the fix was already present before this was filed.
But there was not bug related to it so IMO I think it's fine to leave this as fixed with commit 220b8b7946397b7605e53d97c8b0d3aafe55d4d5. We have done this before, I just can't find an example now :)
I agree.
http://bugs.winehq.org/show_bug.cgi?id=34613
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |220b8b7946397b7605e53d97c8b | |0d3aafe55d4d5
http://bugs.winehq.org/show_bug.cgi?id=34613
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #6 from Alexandre Julliard julliard@winehq.org 2013-12-06 13:44:38 CST --- Closing bugs fixed in 1.7.8.
https://bugs.winehq.org/show_bug.cgi?id=34613
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net Component|-unknown |winemac.drv