That makes sense. I’ll see if I can avoid sub-classing.
I’m still a bit confused by the documentation. What’s the point of overriding JUCEApplication::actionListenerCallback if I can’t add the sub-class as a listener ?
[quote]void JUCEApplication::actionListenerCallback ( const String & message ) [virtual]
Overridden by your subclass to receive the callback.[/quote]
I guess if I do override JUCEApplication::actionListenerCallback, I should call the base class first.
The motivation for adding the ActionListener was to allow the user to quit the application by clicking the close window button in an a-synchronic way. The window will send an action to the application, which will call systemRequestedQuit(). There might be a better way to do it.