Bug #51154 Artifacts on the Canvas when hovering over objects and zooming in/out quickly

Description:
I'd like to report tthe described bug above.
It's quite disturbing that while hovering around the model, every time you are above a line or enter a layer with the cursor, the paint_event() create such massive artifacts.

There have been several improvements in handling the Layer Grabbing handles that i welcomed very much, but instead now the main problem are the disturbing lines flushing the whole time on the working canvas. 

Also noticed, that when zooming in/out quite quickly, there are some font-processing problems due to scale conversion (blurry fonts, must activate the table to see the columns right). 

Hope these uglynesses will disappear for release. Because the rest of the tool is state-of-the-art and a must-have dev-tool.

Regards, Giusi

How to repeat:
Quite on every bigger EER with 15+ tables, error appears to become heavier during working time. Restart fixes it until it starts to reappear again.

Suggested fix:
I guess there is some event-stacking of the Winform Paint() Method hidden somewhere.

Thank you for the bug report. I am not quite sure if I understood what are you reporting; could you please try with release 5.2.16 and if you got the same behavior to show it (if possible) with attached pictures. Thanks in advance.

Hello, I upgraded to .16 but the rendering problems are still here for bigger ERMs.

Please Watch the linked Video (150MB, sorry), watch for the font-blurry on zooming and the Graying out when hovering with cursor over relation-lines.

http://www.casemods.ch/gaming/mysqlwb_rendering_probs.avi

My relevant config:
W7 x64 Ultimate
Intel i7 920
12GB RAM
Geforce 285GTX

How much RAM has your video card?

Hello,

NVidia GeForce GTX285 have 1GB RAM

I attached my DxDiag.txt

another question,

does switching of "draw line crossings" (in preferences->diagram) lower the artifacts?
thanks for your help/patience so far

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".