Offset lines appearing over form after delay (NVIDIA Chipset)

Mark

Hello all -

I'm creating an application that uses a datagridview control. My
development environment is an HP Laptop with a NVIDIA Geforce 4 440 Go
64M.

While using this object, a queer effect occurs where, if you just let
the application sit idle (usually within a minute), the gridlines and
border of the datagridview control will be redrawn over the form.

The exact position of the lines appears to be where the lines SHOULD be
drawn if the form was at (0,0)--it doesn't seem to be transposing the
positions relative to the form location.

The form_paint event is being raised, but I'm not sure why; if I am
using the application normally, the datagridview is constantly being
repainted and this problem doesn't appear. It only appears when the
application is sitting idly.

After these offset gridlines are on the form, they stay on the form
until a repaint is forced (by invalidating the control, or by pulling
the window off the screen's boundaries and pulling it back in.)

I can't figure out WHY this is happening.

I've checked out the event arg's graphic property's members, but
nothing seems to have changed between the original values and the
values of the graphic property when this error occurs.

I've also tried flushing the GDI cache, but that doesn't work either.

I can't tell if these are NEW lines, or lines that are somehow in an
uncleared buffer...

Any help, or even a push in the right direction, would be greatly
appreciated.

Thanks,

-M

Jun 1 '06 #1

James Minns

"Mark" <ma*********@binaryswitch.com> wrote in message
news:11**********************@y43g2000cwc.googlegr oups.com...

Hello all -

I'm creating an application that uses a datagridview control. My
development environment is an HP Laptop with a NVIDIA Geforce 4 440 Go
64M.

While using this object, a queer effect occurs where, if you just let
the application sit idle (usually within a minute), the gridlines and
border of the datagridview control will be redrawn over the form.

[x]

Does the problem go away if you disable hardware acceleration?
It could be a driver problem.

James

Jun 1 '06 #2

Mark

> Does the problem go away if you disable hardware acceleration?

It could be a driver problem.

Yes, after fiddling around with the settings, I found that the problem
when away when I disabled the directdraw and direct3d accelerations.
Alternately, if I disable directdraw from dxdiag, this bug isn't
raised.

I tried update DirectX, but that didn't help. I thought that GDI/GDI+
were a completely seperate animal, so this is surprising...

I've also confirmed this isn't a problem with my code; I have placed an
empty datagridview on a new form and I'm having the same draw problem.

Clearly, asking a user to disable their directdraw accelerations isn't
a solution...

Any ideas?

-M

Jun 2 '06 #3

Ben Voigt

"Mark" <ma*********@binaryswitch.com> wrote in message
news:11**********************@g10g2000cwb.googlegr oups.com...

Does the problem go away if you disable hardware acceleration?
It could be a driver problem.
Yes, after fiddling around with the settings, I found that the problem
when away when I disabled the directdraw and direct3d accelerations.
Alternately, if I disable directdraw from dxdiag, this bug isn't
raised.

I tried update DirectX, but that didn't help. I thought that GDI/GDI+
were a completely seperate animal, so this is surprising...

I've also confirmed this isn't a problem with my code; I have placed an
empty datagridview on a new form and I'm having the same draw problem.

Clearly, asking a user to disable their directdraw accelerations isn't
a solution...

This isn't your app, it's the video card-specific driver. Most of your
users will have zero problems running your application. For the ones with
the troublesome cards, a FAQ entry pointing them to the website of their
video card manufacturer and asking them to update the driver (not DirectX)
is common practice.

Any ideas?

-M

Jun 2 '06 #4