No it's not stupid. But you do need to be careful.
I disagree that DQMH or Actors are in any way required of even recommended based purely on what you have posted. I would first spend some time trying it out with Events as you already have before switching to a completely different way of doing things.
The problem with having a loop feed itself is the problem of infinite loops occurring. This is a similar problem to infinite recursion. If handling Event X fires Event Y which then also fires Event X, you have an infinite loop and you will have problems. This gets really complicated and problematic when it's a conditional relationship, if it only happens under certain circumstances, it can cause ont of those horrible (impossible to reproduce) problems.
- Make sure the number of events you want to fire is bounded (Autoindexing FOR Loop for example)
- Make sure the Event you are calling does not itself create a loop with other events
- If things get complicated, you can also create a helper loop which receives a signal (Loop these items) which then actually send the events back to the actual handler loop. What does this bring? It separates out the control and allows additional methods of debugging if things go weird.
- If you want to get really weird, you can actually have an Event defined with the datatype "Event Registration Refnum" which in turn contains the Events you want to queue up. this gets really weird really quick, but it can be a really cool way to achieve what you want while side-stepping some of the awkward problems which can come along with it.
The fourth point is not to be generally recommended if you're not really comfortable with how Events work.
