Would there be any issue in creating a second DoEvents loop in an event-driven console app?
For example, Method1 needs to wait for Timer2, so Method1 starts a DoEvents loop to give Timer2 a chance to finish. Any problem with that?
One possibility is to split method1 into 2 pieces
1 runs before & the second runs when the timer’s action event fires
Then you can avoid any possible issues
Multiple ways to split it and retain params passed / context (like a context object)
Multiple DoEvents loops I’d expect some odd event firing issues / reentrancy issues like getting data available when you’re in a data available just like a GUI app would
That’s my assumption, just looking for confirmation. Thanks.