Rename create/destroy events to realize/unrealize

As evidence that this was confusing, the documentation for these was an
outright lie, and I've burned quite a bit of time in the past few days trying
to rework things based around that flawed understanding.

These names make it clear what these events actually are.  If we need actual
create/destroy events with a broader scope, they'll have to be added, but I
suspect those aren't actually useful anyway.

1 files changed, 8 insertions, 8 deletions

diff --git a/bindings/cpp/include/pugl/pugl.hpp b/bindings/cpp/include/pugl/pugl.hpp
index d24c52f..267b07c 100644
--- a/bindings/cpp/include/pugl/pugl.hpp
+++ b/bindings/cpp/include/pugl/pugl.hpp
@@ -108,11 +108,11 @@ using EventFlag    = PuglEventFlag;    ///< @copydoc PuglEventFlag
 using EventFlags   = PuglEventFlags;   ///< @copydoc PuglEventFlags
 using CrossingMode = PuglCrossingMode; ///< @copydoc PuglCrossingMode
 
-/// @copydoc PuglCreateEvent
-using CreateEvent = Event<PUGL_CREATE, PuglCreateEvent>;
+/// @copydoc PuglRealizeEvent
+using RealizeEvent = Event<PUGL_REALIZE, PuglRealizeEvent>;
 
-/// @copydoc PuglDestroyEvent
-using DestroyEvent = Event<PUGL_DESTROY, PuglDestroyEvent>;
+/// @copydoc PuglUnrealizeEvent
+using UnrealizeEvent = Event<PUGL_UNREALIZE, PuglUnrealizeEvent>;
 
 /// @copydoc PuglConfigureEvent
 using ConfigureEvent = Event<PUGL_CONFIGURE, PuglConfigureEvent>;
@@ -672,10 +672,10 @@ private:
     switch (event->type) {
     case PUGL_NOTHING:
       return Status::success;
-    case PUGL_CREATE:
-      return target.onEvent(CreateEvent{event->any});
-    case PUGL_DESTROY:
-      return target.onEvent(DestroyEvent{event->any});
+    case PUGL_REALIZE:
+      return target.onEvent(RealizeEvent{event->any});
+    case PUGL_UNREALIZE:
+      return target.onEvent(UnrealizeEvent{event->any});
     case PUGL_CONFIGURE:
       return target.onEvent(ConfigureEvent{event->configure});
     case PUGL_MAP: