Hello
@eue
Some additional ways to investigate, if you need.
1. Visualization depends on mesh prepared on your shape. This mesh is computed using BRepMesh_IncrementalMesh and depends on deflection paramerers provided. So, to improve performance, you may try to change these parameters. The suggestion is using more rude deflection values during the model move by the mouse.
If your algorithms does not prepare this mesh and you don't call this class, StdPrs will do this by itself with some default deflection parameters.
You may try to check a case where the mesh will not be computed at all by StdPrs. To do this, just set the next parameter for AIS_Shape:
C++:
Attributes()->SetAutoTriangulation(Standard_False)
If the mesh was not prepared for the shape, you'll see only the contour of your shape in the viewer. In this case you'll know how much the shaded presentation build takes from the performace point of view.
2. Another or additional way might be the introducing some timer(like QTimer) and reconstruct the shapes by it's ticks? The matter is that the mouse move happens too often and therefore may require too much calls of algo+visualization.
And the question here, what if not StdPrs but prime shape construction takes time? May be it's worth also to check it.)
Regards, Natalia