Why? What's the goal? That's likely (my back-of-envelope review of systems impacted) to be a pretty substantial complication of a lot of systems, so it needs to be a substantial advantage. I have a hard time seeing a use case.
I assume this is meant as a debugging option (similar to the diagram disable structure) and not something that should be changeable at run-time. As such it might not need much code complications. The editor would simply hide the disabled events from the compiler as if they don't even exist but keep them stored somewhere so they can be merged back into the code.
Still, I don't quite see a scenario where this would really be useful. Can you explain?
Just use a Diagram Disable Structure around the event structure, duplicate the disabled code, activate and edit event in one of the copies. Go back to the other version when your debuging is done.
BTW, besides the fact that I remembered having commented on a topic such as this one, I could not remember where this was so I DID A SEARCH for "Disable Event Case".
Here is the snapshot of today's result but that was almost what I got a few days ago:
Lesson: always perform a search whenever you are about to submit an idea. It is no guarantee that you will find a similar one, but if it very obvious or useful, chances are, someone has done it before.
Now of course, I am the best counter-example of this lesson, as I once proposed an idea twice, as I could not find the idea which I thought I had already submitted using the search function, and I concluded that I must have only thought that I had submitted it but had ran out of time or whatever to actually submit it... Naturally, I don't remember which idea that is, so I can't even search for it, but I clearly remember the story. Yes, I do!
