its actually a pretty useful feature, although i have found some bugaboo's with it.
i use visual studio at work, and put the classbrowser, variable windows, and stack on the left monitor. leaving the entire right monitor (less the toolbar of course) for code. schweet.
bugaboo. lunchtime quake3 games require me to disable the 2nd monitor. all fullscreen 3d apps currently require this. however, you can run q3 in a window if your card supports it by hitting alt_enter ingame in q3. it ain't perfect, but it can be done.
also, i have noticed that if i put a window up in the 2nd monitor (like a classbrowser) and then shut down visual studio. and disable the 2nd monitor. and then bring visual studio up again, the class browser is now in 'never-never land'. never to be seen again until you enable that monitor. worse, if you move the ide window to the 2nd monitor now you will (once again) never see the classbrowser as it somehow uses the 2nd monitor as it's base of reference and the other monitor will not display the classbrowser ever!!! it has to do with taking for granted a single monitor, which is not always the case now.
i could go on and on, about how when doing a screencap the wrong screen gets capped, it's possible to disable both monitors thus rendering the system completely useless,etc.
however, when it IS working it really is nice. browsing the polycount forum for metastream models while compiling on the other for example...
wb