I don't use HydraVision, I don't really like it (mainly because when it
"maximizes" a window across multiple displays, it actually
just stretches them, the dialog frame is still the resizing kind, and the
maximize button remains in it's un-maximized state.)
In Hydravision CPL: window control: [checked] Single monitor windows / or
(o) Max to window corners. This will maximize windows to a single monitor.
Well, if You really need mazimize to full desktop, then use ATI CCC\Displays
manager: disable monitor 2, in -- Attached displays currently disabled \
context menu \ Streth main ... on TV or secondary... In the very moment you
decide to play a movie or watch TV, you'll have it disabled for a good long
time :-(
When I said "each window on it's own surface" it was a gues I made, bucase:
when I open several windows, then grab one and start moving it fast all
around, the maximum CPU usage will be 15%. If I unload Window Blinds 5
(WB5) and use GDI, it will be 100% and background windows will have trails
while redrawing. By the way all windows that cannot be skinned from WB5 will
use GDI.
WB5 does not use overlay, because the screen is accessible to CPU
(print-screen) and as You said TV application works (well, not always --
because ATI have good hardware, but poor programming team).
With GDI, when You move a window, You're not only rendering the window to
the new location, but you render all windows that were behind it (pretty
slow). On the other hand You can draw in multiple layers with DirectX, then
You can use DX transformations for minimize / restore effects like in
WindowFX. and Windows Vista. So there's some hardware acceleration.
With direct 3D (D3D) CPU passes images to the (video card -- used as DirectX
filter). It will process them and pass the result back to the CPU, now CPU
can pass it again for another processing or send it to the render (back to
the video card, but this time used as rendering device). This design is
universal, because You can pass streams from one filter to another many
times, but in most cases: You only want to render it so You have 2
additional passes (filter --> CPU --> render, while filter and render are
physically on a same board) and that will degrade the performance. CPU has
access to the streams so You can capture the screen (desktop or games). With
overlay this 2 passes are missing, so CPU can't see what's on the screen
box, but there're advatages: shorter delay and better performance.
By the way, in the performance options for WB5 there's a Hyperpaint setting.
Performance will improve only if it is enabled. I've set it to largest.
Unfortunately despite Stardock claims that WindowBlinds is supported on
Windows 2003, using it on the terminal server may cause disasterous things!
It also causes problems with other tools for accessing remote desktop, like
DameWare mini remote control on XP.
For a fun way to play with the overlay surface, get a copy of Karsten
Sperling's Alpha. It allows you to use the overlay to display
the desktop through whatever color you select. It was originally meant to
allow the command prompt to be "transparent", but you can
set it up to make anything transparent. Set the color key to D4D0C8 and
all of Windows will become transparent.
Well then... The backup operation of my Backup/Testing 2003R2 Server has
just finished, so I'm ready to boot to it and test this program
George Valkov