This one is starting to annoy me. Sometimes when i open dev studio (well most of the time with 1240 now) the VA View appears as a black area to the right of the code window - i.e. just black, no title bars etc. Repeated closing/opening of devstudio is required (plus fiddling with VisualAssistX->Tools->VA View) until it majically draws correctly and i'm able to grab hold of it and dock it with the properties pane as a further tab. But.. when i close down and re-open its back in black - fashionable I'll admit but undesirable.
A quick fix for me would be an option to turn the damn thing off - i don't use it anyhow so at best it's an annoyance. I assume the menu option VisualAssistX->Tools->VA View is supposed to do this but it has no effect. This has happened with previous builds but never as frequently as 1240. Perhaps it's not build related but it's remarkably repeatable today.
Right now, i'm trying desperately not to close VS .NET 2003 to avoid random suffering ;)
VAX version 1246 XP Pro SP1 Dev Studio ver 7.1.3088 Dell Precision 520 (2 procs) Radeon VE AGP video card (dual head)
I can make the problem go away without having to reset my views (painful)...
Toggle the Tools->VA View option Restart dev studio Toggle the Tools->VA View option again (to view the caption bar for the view) Float the VA View Restart dev studio
Yes, this is a little painful, but less so than rearranging all of my views following a reset.
I have the same problem. It's a little hard to 'float and close the window' when it shows up as unresponsive black space. I have to disable VAX, restart dev studio, close the VA View window (that's now not black), re-enable VAX.
WinXP SP1 dual monitors off 1 card (GeForce FX 5200) VS2k2/VC7.0
I am also experiencing this problem. Here's my setup:
VAX version 1246 XP Pro SP2 Beta2 Dev Studio ver 7.1.3088 NVidia GeForce FX 5600 AGP video card (dual head)
It definitely appears to be a bug related to having a dual-monitor setup with the main window on one monitor and the floating windows on the second monitor.
This is just a "me, too" post. It's a great product; I'll buy it if they get this bug fixed.