|
| 1 | +# DisplayManager Event System Usage Examples |
| 2 | + |
| 3 | +This document demonstrates how to use both the legacy DisplayListener interface and the new EventDispatcher-based event system. |
| 4 | + |
| 5 | +## Legacy API (Backward Compatibility) |
| 6 | + |
| 7 | +```cpp |
| 8 | +#include "nativeapi.h" |
| 9 | +using namespace nativeapi; |
| 10 | + |
| 11 | +// Option 1: Implement DisplayListener interface |
| 12 | +class MyDisplayListener : public DisplayListener { |
| 13 | +public: |
| 14 | + void OnDisplayAdded(const Display& display) override { |
| 15 | + std::cout << "Display added: " << display.name << std::endl; |
| 16 | + } |
| 17 | + |
| 18 | + void OnDisplayRemoved(const Display& display) override { |
| 19 | + std::cout << "Display removed: " << display.name << std::endl; |
| 20 | + } |
| 21 | +}; |
| 22 | + |
| 23 | +void useLegacyAPI() { |
| 24 | + DisplayManager displayManager; |
| 25 | + MyDisplayListener listener; |
| 26 | + |
| 27 | + // Register listener |
| 28 | + displayManager.AddListener(&listener); |
| 29 | + |
| 30 | + // Events will be received via OnDisplayAdded/OnDisplayRemoved |
| 31 | + |
| 32 | + // Don't forget to remove when done |
| 33 | + displayManager.RemoveListener(&listener); |
| 34 | +} |
| 35 | + |
| 36 | +// Option 2: Use DisplayEventHandler with callbacks |
| 37 | +void useLegacyCallbackAPI() { |
| 38 | + DisplayManager displayManager; |
| 39 | + |
| 40 | + DisplayEventHandler handler( |
| 41 | + [](const Display& display) { |
| 42 | + std::cout << "Display added: " << display.name << std::endl; |
| 43 | + }, |
| 44 | + [](const Display& display) { |
| 45 | + std::cout << "Display removed: " << display.name << std::endl; |
| 46 | + } |
| 47 | + ); |
| 48 | + |
| 49 | + displayManager.AddListener(&handler); |
| 50 | + // ... use the handler |
| 51 | + displayManager.RemoveListener(&handler); |
| 52 | +} |
| 53 | +``` |
| 54 | +
|
| 55 | +## New Event API (Recommended) |
| 56 | +
|
| 57 | +```cpp |
| 58 | +#include "nativeapi.h" |
| 59 | +using namespace nativeapi; |
| 60 | +
|
| 61 | +// Option 1: Use callback functions (simplest) |
| 62 | +void useNewEventAPI() { |
| 63 | + DisplayManager displayManager; |
| 64 | + |
| 65 | + // Register event listeners with callbacks |
| 66 | + auto addedListenerId = displayManager.AddEventListener<DisplayAddedEvent>( |
| 67 | + [](const DisplayAddedEvent& event) { |
| 68 | + const Display& display = event.GetDisplay(); |
| 69 | + std::cout << "Display added: " << display.name << std::endl; |
| 70 | + }); |
| 71 | + |
| 72 | + auto removedListenerId = displayManager.AddEventListener<DisplayRemovedEvent>( |
| 73 | + [](const DisplayRemovedEvent& event) { |
| 74 | + const Display& display = event.GetDisplay(); |
| 75 | + std::cout << "Display removed: " << display.name << std::endl; |
| 76 | + }); |
| 77 | + |
| 78 | + // Events will be dispatched automatically |
| 79 | + |
| 80 | + // Remove listeners when done |
| 81 | + displayManager.RemoveEventListener(addedListenerId); |
| 82 | + displayManager.RemoveEventListener(removedListenerId); |
| 83 | +} |
| 84 | +
|
| 85 | +// Option 2: Implement TypedEventListener (for complex logic) |
| 86 | +class MyDisplayEventListener : public TypedEventListener<DisplayAddedEvent> { |
| 87 | +public: |
| 88 | + void OnTypedEvent(const DisplayAddedEvent& event) override { |
| 89 | + const Display& display = event.GetDisplay(); |
| 90 | + std::cout << "New display detected: " << display.name << std::endl; |
| 91 | + // Complex logic here... |
| 92 | + } |
| 93 | +}; |
| 94 | +
|
| 95 | +void useNewEventAPIWithListener() { |
| 96 | + DisplayManager displayManager; |
| 97 | + MyDisplayEventListener listener; |
| 98 | + |
| 99 | + auto listenerId = displayManager.AddEventListener<DisplayAddedEvent>(&listener); |
| 100 | + |
| 101 | + // ... use |
| 102 | + |
| 103 | + displayManager.RemoveEventListener(listenerId); |
| 104 | +} |
| 105 | +
|
| 106 | +// Option 3: Use EventDispatcher directly |
| 107 | +void useEventDispatcherDirectly() { |
| 108 | + DisplayManager displayManager; |
| 109 | + EventDispatcher& dispatcher = displayManager.GetEventDispatcher(); |
| 110 | + |
| 111 | + auto listenerId = dispatcher.AddListener<DisplayAddedEvent>( |
| 112 | + [](const DisplayAddedEvent& event) { |
| 113 | + // Handle event |
| 114 | + }); |
| 115 | + |
| 116 | + // You can also dispatch custom events if needed |
| 117 | + Display customDisplay; |
| 118 | + customDisplay.name = "Custom Display"; |
| 119 | + dispatcher.DispatchSync<DisplayAddedEvent>(customDisplay); |
| 120 | + |
| 121 | + dispatcher.RemoveListener(listenerId); |
| 122 | +} |
| 123 | +``` |
| 124 | + |
| 125 | +## Migration Guide |
| 126 | + |
| 127 | +### From Legacy to New API |
| 128 | + |
| 129 | +```cpp |
| 130 | +// OLD WAY |
| 131 | +class OldListener : public DisplayListener { |
| 132 | + void OnDisplayAdded(const Display& display) override { |
| 133 | + handleDisplayAdded(display); |
| 134 | + } |
| 135 | + void OnDisplayRemoved(const Display& display) override { |
| 136 | + handleDisplayRemoved(display); |
| 137 | + } |
| 138 | +}; |
| 139 | + |
| 140 | +DisplayManager manager; |
| 141 | +OldListener listener; |
| 142 | +manager.AddListener(&listener); |
| 143 | + |
| 144 | +// NEW WAY |
| 145 | +DisplayManager manager; |
| 146 | +auto addedId = manager.AddEventListener<DisplayAddedEvent>( |
| 147 | + [](const DisplayAddedEvent& event) { |
| 148 | + handleDisplayAdded(event.GetDisplay()); |
| 149 | + }); |
| 150 | +auto removedId = manager.AddEventListener<DisplayRemovedEvent>( |
| 151 | + [](const DisplayRemovedEvent& event) { |
| 152 | + handleDisplayRemoved(event.GetDisplay()); |
| 153 | + }); |
| 154 | +``` |
| 155 | +
|
| 156 | +### Benefits of New API |
| 157 | +
|
| 158 | +1. **Type Safety**: Compile-time checking of event types |
| 159 | +2. **Flexibility**: Can use lambdas, function pointers, or listener classes |
| 160 | +3. **Advanced Features**: Async dispatch, listener management by ID |
| 161 | +4. **Consistency**: Same event system used across the entire library |
| 162 | +5. **Extensibility**: Easy to add new event types without changing interfaces |
| 163 | +
|
| 164 | +### Backward Compatibility |
| 165 | +
|
| 166 | +The legacy DisplayListener interface is fully supported and will continue to work. Both systems can be used simultaneously - events will be dispatched to both old and new listeners. |
| 167 | +
|
| 168 | +## Best Practices |
| 169 | +
|
| 170 | +1. **Prefer the new event API** for new code |
| 171 | +2. **Use callback functions** for simple event handling |
| 172 | +3. **Use TypedEventListener classes** for complex event handling logic |
| 173 | +4. **Always remove listeners** to prevent memory leaks |
| 174 | +5. **Store listener IDs** returned by AddEventListener for later removal |
| 175 | +6. **Consider using RAII** to automatically manage listener lifetimes |
| 176 | +
|
| 177 | +## Event Types |
| 178 | +
|
| 179 | +- `DisplayAddedEvent`: Fired when a display is connected |
| 180 | +- `DisplayRemovedEvent`: Fired when a display is disconnected |
| 181 | +
|
| 182 | +Both events provide access to the `Display` object via `GetDisplay()` method. |
0 commit comments