Implementing a system to enable text-based dynamic construction and dispatch of Events.
Simply create a TLKEventSandboxHandler<TMyEventType> class, override a few methods to define a "Command Name" (a sane, human-readable identifier for the Event Type) as well as a "help" response (list of Parameters and their expected Value Types), and finally the "interpreter" to extract from the Console Command String the correct Values for the Event, then Validate the Values before dispatching it to the Queue/Stack/Scheduler.
This will provide a more "manual" way to test Event Hookups throughout the system without the added complexity of providing GUI editors for your Value Types.
Related heavily to issue #123
Implementing a system to enable text-based dynamic construction and dispatch of Events.
Simply create a
TLKEventSandboxHandler<TMyEventType>class, override a few methods to define a "Command Name" (a sane, human-readable identifier for the Event Type) as well as a "help" response (list of Parameters and their expected Value Types), and finally the "interpreter" to extract from the Console Command String the correct Values for the Event, then Validate the Values before dispatching it to the Queue/Stack/Scheduler.This will provide a more "manual" way to test Event Hookups throughout the system without the added complexity of providing GUI editors for your Value Types.