Talk:Minesweeper game: Difference between revisions
→Differences in behavior from classic game: Win32 GUI API and security policies
(→Differences in behavior from classic game: Win32 GUI API and security policies) |
|||
Line 26:
: Interesting feature. I believe the cheat was taken away before XP. --[[User:Dgamey|Dgamey]] 03:01, 12 July 2010 (UTC)
:: Could well be. It relied on being able to toggle a pixel in the corner of the screen directly, which I can imagine didn't fit well with the display management model updates that happened in the NT line of kernels. –[[User:Dkf|Donal Fellows]] 08:42, 12 July 2010 (UTC)
::: With Windows, that's abstracted away with Win32 (the API set, which oddly was available on Windows 3.1 and earlier). All graphic access in Windows prior to DirectX is done was a device-neutral fashion; a program could conceivably operate the same way on a printer framebuffer as it did on a monitor. The call sequence is the same (Get a handle to the device context, get a handle to the bitmap for the device context, lock the bitmap to get a buffer pointer, unlock bitmap, unlock the device context.), and any Win32 app can grab the NULL DC, which is assumed by the system to mean the full desktop. (Pretty easy way to test your coord-calculating logic in your code, actually.)
::: The easter egg apparently disappeared in XP SP2, which had a lot of security improvements. If I had to guess, I'd say that corner pixel violated some security policy that didn't have a basis in technical limitations, like covering part of the screen that didn't belong to the app and didn't serve a core app role. --[[User:Short Circuit|Michael Mol]] 12:34, 12 July 2010 (UTC)
| |||