I don’t see anything in RhinoCommon. But the Rhino C++ SDK does contain a CRhinoDisplayModeChanged event class. I’ll put this on the to-do for @stevebaer. Hopefully we can add something for a future service release.

Just curious, why do you need to be notified with the display mode changes?

I noticed that a display conduit I use does not get redrawn immediately when the user changes display mode, so I was hoping that it could be notified of the change and tell the document to redraw its views. It gets redrawn if the user changes the camera though.

So, another way to solve this is to issue a RhinoDoc.ActiveDoc.Views.Redraw() after the display mode has changed.

I noticed that a display conduit I use does not get redrawn immediately when the user changes display mode

This sounds like a bug we need to fix. I couldn’t repeat this in Rhino. I hooked up to the PostDrawObjects event and it got called when switching display modes back and forth between wireframe and shaded. This is essentially the exact same as having a conduit with that specific virtual function overridden. Do you have a small sample that shows Rhino not calling the conduit when the display mode changes.

This seems to be a bug. To reproduce it use the DisplayConduit and Command as below.

The display conduit will draw a red point in the center of the bounding box of the selected surface.

Now, change the display mode without changing the camera and the red point disappears. The DrawOverlay method gets called (there is output on the commandline after the change of display mode), but the red point is not drawn! A change in the camera will trigger a new DrawOverlay and then the point gets drawn.