Dual monitor woes
-
Not long ago I bought a second monitor, but VS 2005 doesn't seem to like it one bit. If I maximize VS in either of the two monitors it works just fine. If I maximize VS to cover both monitors entirely (I want to use both monitors so I can use "Vertical tab groups" to have several files visible at the same time) the application becomes unresponsive, but only on the PRIMARY monitor. I can write code just fine on my secondary monitor, everything's smooth, including code completion and visual assist tips. On the primary monitor my CPU spikes to 100% for roughly 5 seconds for every keypress. Does anybody know of a quick fix? Thanks a million!
-
Not long ago I bought a second monitor, but VS 2005 doesn't seem to like it one bit. If I maximize VS in either of the two monitors it works just fine. If I maximize VS to cover both monitors entirely (I want to use both monitors so I can use "Vertical tab groups" to have several files visible at the same time) the application becomes unresponsive, but only on the PRIMARY monitor. I can write code just fine on my secondary monitor, everything's smooth, including code completion and visual assist tips. On the primary monitor my CPU spikes to 100% for roughly 5 seconds for every keypress. Does anybody know of a quick fix? Thanks a million!
generic_user_id wrote:
Does anybody know of a quick fix?
What graphics card are you using, which mode is used to supply the dual monitor, what version of drivers? and have you looked to see if there is a later driver with a bugfix related to dual monitor support? _________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
generic_user_id wrote:
Does anybody know of a quick fix?
What graphics card are you using, which mode is used to supply the dual monitor, what version of drivers? and have you looked to see if there is a later driver with a bugfix related to dual monitor support? _________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
I'm using the most recent NVidia drivers and a 5600 ultra vid card. (One digital out, one analog.) But I doubt my video card is to blame, all other applications work fine on both monitors - it's just visual studio that lets me down.
-
I'm using the most recent NVidia drivers and a 5600 ultra vid card. (One digital out, one analog.) But I doubt my video card is to blame, all other applications work fine on both monitors - it's just visual studio that lets me down.
generic_user_id wrote:
But I doubt my video card is to blame, all other applications work fine on both monitors - it's just visual studio that lets me down.
True, but each application can try to access the card directly, and bugs in the drivers mean that performance and operation of one application does not necessarily apply to another. I wasn't thinking video card being to blame per se, but trying to figure out where you were in the hardware->driver->application arena. If all applications played by the same rules, then yes, all applications would be compatible with the drivers in the same way. Since competition demands you "out-do" your apponent, we developers tend to bend the rules a bit and access hardware through various means, driver modes, vendor extensions and windows commands, and thus each application gets different compatibility and performance. Even I cheat once in a while and access vendor extensions to beat out my competition. But if I did not, why bother signing up as an nVidia developer? :) I take it you are running horizontal span for your nView mode? is your primary monitor on the top or the bottom are there any 3D apps open, even with display minimized -- i.e. folding, seti, etc.? these can hold a graphics mode open activating a bug in the 5000 series related to the which graphics port you have open and any two applications accessing the driver in parallel. Are you using one port as digital and one as analog to a digital and analog monitor? or are you converting both signals to analog VGA to go to two analog monitors? Latest driver being 84.21 release candidate? or 84.24 beta? or 81.98 certified? _________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) -- modified at 14:28 Saturday 8th April, 2006
-
generic_user_id wrote:
But I doubt my video card is to blame, all other applications work fine on both monitors - it's just visual studio that lets me down.
True, but each application can try to access the card directly, and bugs in the drivers mean that performance and operation of one application does not necessarily apply to another. I wasn't thinking video card being to blame per se, but trying to figure out where you were in the hardware->driver->application arena. If all applications played by the same rules, then yes, all applications would be compatible with the drivers in the same way. Since competition demands you "out-do" your apponent, we developers tend to bend the rules a bit and access hardware through various means, driver modes, vendor extensions and windows commands, and thus each application gets different compatibility and performance. Even I cheat once in a while and access vendor extensions to beat out my competition. But if I did not, why bother signing up as an nVidia developer? :) I take it you are running horizontal span for your nView mode? is your primary monitor on the top or the bottom are there any 3D apps open, even with display minimized -- i.e. folding, seti, etc.? these can hold a graphics mode open activating a bug in the 5000 series related to the which graphics port you have open and any two applications accessing the driver in parallel. Are you using one port as digital and one as analog to a digital and analog monitor? or are you converting both signals to analog VGA to go to two analog monitors? Latest driver being 84.21 release candidate? or 84.24 beta? or 81.98 certified? _________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) -- modified at 14:28 Saturday 8th April, 2006
I solved the problem - it didn't have to do with dual monitors. For some reason, the problem was caused by a typo in one of the source files I was editing in VS - intellisense got upset. I thought it had to do with dual monitors because I had one cpp file open on one monitor, and one on the other. So at the same time I made a typo in the source code and I made the window span both monitors... I did all testing afterward with the same files (and in the same arrangement), so every test I did confirmed my dual monitor hypothesis. Anyway, thanks for the effort Jeffry.
-
I solved the problem - it didn't have to do with dual monitors. For some reason, the problem was caused by a typo in one of the source files I was editing in VS - intellisense got upset. I thought it had to do with dual monitors because I had one cpp file open on one monitor, and one on the other. So at the same time I made a typo in the source code and I made the window span both monitors... I did all testing afterward with the same files (and in the same arrangement), so every test I did confirmed my dual monitor hypothesis. Anyway, thanks for the effort Jeffry.
generic_user_id wrote:
Anyway, thanks for the effort Jeffry.
I tried.... I have been dual monitor so long, I think I have experienced (almost) every bug in existance related to nView (and a few in ATI, though I only used two ATI machines in 6 years). glad you fixed it! :) _________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)