David Burton wrote:
With callbacks, if, when your application gets a button clock or whatever, it then tries to do more user interactions, it will be reentering the GUI code for a new user interaction from deep within the GUI code itself,
Yes, this is the way modal dialogs are implemented in many GUI frameworks, using a nested event loop, and I've never found it to be a problem, as long as you really do intend the interaction to be modal. If it needs to be non-modal, then you're going to have to break it up into stages that are called one at a time from the top level. Then it doesn't make much difference if the first stage is triggered directly from a button callback or from a handler for a custom event. -- Greg