Hide and Display AIS_ColoredShape - C# Wrapper

AIS_ColoredShape doesn't deal with OCAF directly - it stores only TopoDS_Shape and assigning colors/materials. Hence, on its own it cannot be affected by any OCAF operations like Undo/Redo. (In contrast, XCAFPrs_AISObject computes presentation from TDF_Label, thus taking TopoDS_Shape and colors from XDE document, when recomputed).

How AIS_ColoredShape is filled in in your case and updated by Undo/Redo operation is unclear to me.

This is part of the class where the AIS_ColoredShape is created:

TopoDS_Compound compound;
TopoDS_Shape shapeCompound;
BRep_Builder builder;
AIS_ColoredShape aisCompound = null;
AIS_InteractiveContext myContext;

public class CustomCompoundAIS : AIS_Shape
{

    public CustomCompoundAIS(TopoDS_Compound shapeComp) : base(shapeComp)
    {
        compound = shapeComp;
        shapeCompound = compound;
        builder = new BRep_Builder();
        builder.MakeCompound(ref compound);
    }

    public void GenerateCompound()
    {
        aisCompound = null;

        if (shapes.Count > 0)
        {

            aisCompound = new AIS_ColoredShape(shapeCompound);

            for (int i = 0; i < shapes.Count; i++)
            {
                builder.Add(ref shapeCompound, shapes[i]);
            }


            // Triangulation
            var mesher = new BRepMesh_IncrementalMesh(shapeCompound, 0.3, false, 0.5, true);
            mesher.Perform();


            var shading = new Prs3d_ShadingAspect();
            var mat = new Graphic3d_MaterialAspect(Graphic3d_NameOfMaterial.Graphic3d_NOM_PLASTIC);
            shading.SetMaterial(mat);
            aisCompound.Attributes().SetShadingAspect(shading);


            for (int i = 0; i < shapes.Count; ++i)
            {
                var col = DecodeColor(materials[i].Color);
                aisCompound.SetCustomColor(shapes[i], col);
            }


            // Display as a single object and limit selection to the entire shape
            myContext.Display(aisCompound, true);
            myContext.SetDisplayMode(aisCompound, (int)AIS_DisplayMode.AIS_Shaded, true);
        }
    }

    public AIS_ColoredShape GetAISColoredShape()
    {
        return aisCompound;
    }
}

Then, the AIS_ColoredShape is stored in a dictionary to be recovered later

I have found what seems to be the solution. I was hiding the objects using the method Remove from AIS_InteractiveContext. Using Erase instead seems to solve my issues.

Honestly, I do not understand what is different about using one method or the other

Honestly, I do not understand what is different about using one method or the other

The difference between AIS_InteractiveContext::Remove() and ::Erase() is that the first one removes object completely from Context and cleans up all computed presentations - so that within the next ::Display() they should be recomputed anew. ::Erase() only marks object as hidden one, but keeps it computed presentations in memory so that ::Display() later on will reuse them.

Cannot reproduce described side effects from the given code snippets - so I guess the issue happens due to some other factors or another code. Which OCCT version is used by the way?

            var mesher = new BRepMesh_IncrementalMesh(shapeCompound, 0.3, false, 0.5, true);
            mesher.Perform();

BRepMesh_IncrementalMesh called like this will perform meshing twice - within the constructor and then by called ::Perform().

            aisCompound = new AIS_ColoredShape(shapeCompound);
            for (int i = 0; i < shapes.Count; i++)
            {
                builder.Add(ref shapeCompound, shapes[i]);
            }

This works in this case, but logically you should construct TopoDS_Compound first and then pass it to AIS_ColoredShape. Once constructed, TopoDS_Shape is expected to be an immutable object, so that adding/removing subshapes shouldn't be done afterwards - instead a copy should be created and filled in. One TopoDS_Shape is added as subshape to another TopoDS_Shape it is also marked 'Frozen' and attempts to modify it via BRep_Builder::Add() and similar will throw TopoDS_FrozenShape exception.

public class CustomCompoundAIS : AIS_Shape

What AIS_Shape does here? How created AIS_ColoredShape is linked to AIS_Shape?

            myContext.Display(aisCompound, true);
            myContext.SetDisplayMode(aisCompound, (int)AIS_DisplayMode.AIS_Shaded, true);

Pay attention to theToUpdateViewer flag within AIS_InteractiveContext methods. When give it true in a row, this means that Viewer will be redrawn multiple times, and you might see intermediate steps as blinking frames.

Thank you very much. You have spotted several things in the code I did not realize about. I'm very new using the Open Cascade library and I'm learning lots of thing the hard way.

I'm using Open Cascade 8.1 with the c# wrapper comertialized by Open Cascade. Just as a comment I have found several things that work different from the c++ version due (probably) for the extra abstraction layer of the wrapper and how memory is treated