From ba11bb80c96fc9c9124ba2fa929425f558f86824 Mon Sep 17 00:00:00 2001 From: David Robillard Date: Sat, 7 Jan 2023 19:27:05 -0500 Subject: 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. --- bindings/cpp/include/pugl/pugl.hpp | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) (limited to 'bindings') 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; +/// @copydoc PuglRealizeEvent +using RealizeEvent = Event; -/// @copydoc PuglDestroyEvent -using DestroyEvent = Event; +/// @copydoc PuglUnrealizeEvent +using UnrealizeEvent = Event; /// @copydoc PuglConfigureEvent using ConfigureEvent = Event; @@ -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: -- cgit v1.2.1