Windows 7: Remove Show Desktop Button

The real culprit for new (2010) software are vendors that ignore the "Causes Validation Event" as the mouse cursor drags across a label or other tool on the windows form. [The value for Causes Validation should be false unless there is a specific reason to use event handling for the tool that appears on the windows form.] If, for instance, the operating system cursor (usually arrow) is different from the cursor selected by the software vendor, this property causes the cursor value in the label property window, say "NoMove2d", to be generated, but Microsoft compounded the problem because Microsoft generates the new cursor "NoMove2d" without transferring the original coordinates of "Arrow" to "NoMove2d" as a starting point for a smooth transition. Consequently, the "NoMove2d" then appears in a "clock tick instant" at the highest screen coordinates(lower right), whereupon it generates the event handler for "Show Desk Top" as the next mouse move event happens. The operator does not know what hit him!!!!! Older software does not have a fix, and I should note that before 2010, there was no consequence for ignoring "Causes Validation."

The testing department at Microsoft dropped the ball on this. Probably they tested software where this feature wasn't ignored, and consequently; they were oblivious to the event taking place. Now I think they simply duck the issue. What this 2010 change means is that older software is not really backwards compatible. They should have never put anything with an event handler at (0,0) or (max,max)!

A totally agree with you people, complaining about the damn Show Desktop button!

Imagine how "useful" is when using multiple displays and you mouse cursor gets stuck in the right bottom corner when moving from one screen to another.

For those who are using the Recycle Bin and a clean desktop, here's a little tool that will place the Recycle Bin in the system tray: http://www.e-sushi.net/minibin/

It's really useful!

In order to remove the Show Desktop button do the following:

Use this tool first: http://www.door2windows.com/windows-7-show-desktop-button-remover-remove-windows-7-show-desktop-button-with-one-click/

then this one: http://www.thewindowsclub.com/remove-and-restore-show-desktop-button-with-showdesktop-remover

But the cursor still gets stuck to the right bottom of the screen when you move it to the next screen.

If you guys think this button is F#C*ing annoying with a mouse, imagine how annoying it is with a pen. Every time I put my hand on the screen to write something or click something with my tablets pen it goes to desktop. Seriously windows get your sh!t together. Now that windows 7 slates and tablets are becoming popular this becomes more than just an eyesore, it is a real issue when the palm of your hand sends you to your desktop every time you try to write, click, or do any kind of input.

This feature is actually more dangerous than it looks for two reasons should that require Microsoft addressing this feature. Often over looked when writing programs in Visual Studio is the reaction of the cursor as it passes over a control, such as a label. For example, often the label's 'Cursor' and 'Enabled' property gets ignored by the programer because the label is just instructional and otherwise not important. On certain computer models, (and especially HP Laptops equipped with mouse pads), an event is triggered that slams the mouse cursor to the far lower right corner of the screen as the Mouse Cursor too quickly changes from the users cursor style choice to the default cursor choice that was specified in the control. (I am only guessing here that the video placement of the new cursor position is threaded, and since a number is not available yet, the register is the highest clip region value of the screen by default.) Quite often the show desk top gets triggered when this happens and the user's program from thier perspective just seems to disappear! Neither the programmer nor the client are completely aware of what is happening. In addition to this, this also causes problems in the AMD screen drivers and Intel Drivers of certain computer models. There is a lot of software out there where there was neither 'blood nor fowl' when ignoring label control properties. It used to not matter until recent hardware changes, but many issues surrounding the "unexplained behavior" still gets ignored by Microsoft.

For this reason, it is simply "bad practice" for Microsoft to land anything in the upper left, or lower right corner by default. Win7 for instance might not be considered backwards compatible for this reason, but for its decision to place something that functions by default in a 'danger zone!' It is impractical to suggest that all existing software out there should be discarded.