Project Natal uses several technologies simultaneously to capture and replicate a player's motion on-screen and in-game. Natal, which could be readily described as a Wii sensor bar on sterois, uses an RGB camera, intelligent depth sensor, and multiarray microphone to collect voice commands, video, and movement with realtime physics, which is then processed by a brand new processing unit and proprietary software. As you would expect the RGB camera is used for video and picture capture, as well as facial recognition, but the real technological meat and potatoes of the device is it's depth sensor and processing. Project Natal's depth sensor detects 3-D space through the use of a monochrome CMOS sensor and an infrared projector. The pairing of these two technologies, Microsoft says, makes Natal capable of detecting movement, orientation, and gestures in any lighting environment. Project Natal's processing is what brings all of the data together, and can differentiate between players and their environment, as well as detect specific body parts, from arms and legs to even a player's head.
Загрузить Punto Switcher 2.96
(версия от 14 мая 2008 года с поддержкой Windows Vista, обновлены правила, исправлены проблемы с UAC)
Why does the taskbar default to the bottom of the screen?
It didn't always.
The original taskbar didn't look at all like what you see today. It defaulted to the top of the screen and looked something like this.
This is definitely not what it actually looked like. It has been so long I forgot precisely what it looked like (I didn't realize there was going to be a quiz ten years later), but this captures the basic flavor, at least for the purpose of this discussion.
The point is that the bar took the form, not of buttons, but of tabs. Each tab corresponded to a running window, which melded into the tab. You switched window by clicking the corresponding tab.
You can see vestiges of this style in the TCS_BUTTONS style in the tab control. When we switched to the button-look for the taskbar, we still had a lot of switching code based on the tabs metaphor, and it was less work to add a button-look to the tab control than it was to rewrite all the switching code.
The tabbed look was abandoned for various reasons, one of which was what everybody else has already noticed: If you put the taskbar at the top of the screen, lots of windows end up sliding under it, because they assumed that the usable area of the screen began at (0,0). Other windows would "creep" up the screen because they used GetWindowPlacement to save their window position (which returns workspace coordinates, where (0,0) is the first usable pixel) but use SetWindowPos to restore it (which uses screen coordinates, where (0,0) is the upper left pixel of the primary monitor).
There were too many apps that kept sliding under the top-docked taskbar so we had to abandon that idea and move it to the bottom.
It's somewhat disheartening to observe that now, eight years later, apps still mess up their coordinate systems and keep sliding under a top-docked or left-docked taskbar.