GMWolf
aka fel666
We need a suggestion label.
Often when working with GM, I would like to keep the clicked evevents, etc, But use my own code to trigger the event - This is used a lot in GUI design, etc. This is already possible, but the problem remains that the event will still be triggered by GMEngine.
The solution so far was to register scripts as events, Perhaps using a naming scneme and reflection to automate the process. But this defeats the point of having Objects with events.
What I suggest is that we have the ability to disable some events for objects and instances. This way, the code will only run when called using event_perform or event_perform event.
This has many advantages over current solutions:
Often when working with GM, I would like to keep the clicked evevents, etc, But use my own code to trigger the event - This is used a lot in GUI design, etc. This is already possible, but the problem remains that the event will still be triggered by GMEngine.
The solution so far was to register scripts as events, Perhaps using a naming scneme and reflection to automate the process. But this defeats the point of having Objects with events.
What I suggest is that we have the ability to disable some events for objects and instances. This way, the code will only run when called using event_perform or event_perform event.
This has many advantages over current solutions:
- We get to keep the interface GM offers,
- easier to port from GM event triggerin to custom event triggering,
- prevents cluttering the resource tree with loose scripts
- makes it much easier when dealing with inheritance.