Hi,

In its MouseDown handler FlowChart.NET marks all links and subordinate items attached to the main one as being modified. It also draws the non-modified items in an offscreen cache image used later to repaint the screen quickly. Then when processing MouseMove, only the items marked as being modified are redrawn. So it is a bit later to attach the lower lanes in BoxModifying, which is raised for the first time when the mouse moves.

You might attach the items in MouseDown, or create a custom Behavior object and attach them in its StartDraw method. If that won't work for you, next week we can add some StartDrag_ events that will let you attach items before the control starts tracking the modification.

Stoyan

Hi,
Ok...the attaching works fine but now I have another problem that I noticed...this occurs after detaching the boxes. Again there are strange flickers to all objects; exception is the object I resized; When I move a box over other boxes it does not draw them at all.
I tried to call "RecreateCacheImage()" at mouse up after detaching but it makes no difference.


Tks.

Try detaching the boxes from the BoxModified event raised for the master box.

Stoyan

It was the opposite to the attaching problem - the items marked as being modified have their modification flag cleared just after raising the MouseUp event. So if you detach boxes from the MouseUp handler, the flowchart will not reach them while traversing the items being dragged, and won't clear their 'being-dragged' flag.

We could fix that by moving MouseUp raising code to the end of our OnMouseUp override, but this could lead to other problems.

Stoyan