Another use case might be if you have 3 buttons. The first two each perform a different action. The third button performs both of those actions and is provided as a shortcut for the user. I hadn’t seen the SequenceCommand before, so that could be used to solve this. But perhaps a more elegant solution would be to hook up that third event to the first two commands.

This is the first time we’ve run into this, it’s certainly not an often-needed feature.

It’s funny to see which blog posts end up getting the most feedback…

While you would still have to register an event for each of the commands, you would only have to dispatch one event to automatically cause the rest of the commands to be executed.

Multiple controllers is a bad smell as well for me; unless the commands the controller is handling are completely exclusive of each other (which to me would be refactoring towards 2 separate applications/modules). The whole point of the controller is a single switch to decide on how to handle a user-gesture; if you have multiplicity in your controllers, the extreme case (1 controller per event) has now just made your controller redundant.

Use-cases would help, code would help even more, in helping to understand what you’re trying to achieve, and whether Cairngorm is preventing you actually, or as I suspect, artificially.

It’s ok to colour outside the lines.

Good idea bout the multiple controllers, that would work for this.

You _can_ have more than one command per event, but the must be registered in separate controllers. I’ve worked around this by mapping an event to an “aggregate” command that creates and runs the N other commands involved. Nasty stuff, and a design flaw in Cairngorm IMHO.