....
>
> Does anyone have an idea?
First the background. The graph typically erases, draws the grid if
visible, then draws the plots into an offscreen bitmap. The bitmap is
then drawn to the window all at once, and this help to get rid of the
flickering since you will not see a graph half erased in one video
refresh, erased and half gridded, then gridded with some of the plots as
intermediate displays.
The graph cursors are not drawn into the bitmap so that they are better
animated when someone grabs one and drags it around the plots. If the
cursor is drawn into the bitmap, then how do you erase the cursor in its
old location? By redrawing a sliver of graph, which takes awhile. If
the cursor is drawn straight to the window and everything el
se is in the
bitmap, then you can draw a sliver of the bitmap to the window whenever
you want to erase a cursor. And of course the tradeoff is that if the
cursor is drawn to the window it flickers a little bit, but animates
well. If drawn with the plots to the bitmap, it flickers not at all,
but animates poorly.
We tried to improve this around LV5 or so by making a distinction
between cursors that were movable by the end user and those that were
not. Problem is that some users also animate cursors using property
nodes. Oops. So the improvement was removed, sort of.
In your .ini file, if you set smoothGraphMarkers to TRUE, and disable
user interaction with your cursors, you will get smoother cursors. If
you animate the cursors using property nodes once the plot is up, this
will take longer, and of course it doesn't allow the user to grab and
move the cursors, but maybe it will help.
Greg McKaskle