Well, in your scenario, either
1) The initial mediator either needs to keep state (which button was initially pressed) - not good: outside the mediator's clearly defined responsibilities.
2) The view component needs to hang onto the information about which button was pressed (and possibly clear it after you've checked it again - kind of a hassle.
Instead, consider using a transient Proxy.
You've got some info you need to hang onto for an indeterminate amount of time while you do some other, asynchronous stuff. In your simple scenario you may 'know' where the original event / notification came from, but in other such situations you may not. The transient Proxy allows you to decouple the source of the event / notification from the processing of it later.
It goes something like this:Inside your Mediator:
private function handleStartAndJumpEvent(event:Event):voidLater in your StartCommand
facade.registerProxy( new Proxy( AppConstants.START_ACTION, AppConstants.START_AND_JUMP ) );
private function handleStartEvent(event:Event):void
facade.registerProxy( new Proxy( AppConstants.START_ACTION, AppConstants.START ) );
, which needs to know how you started, simply retrieve the transient Proxy:
var startHow:String = facade.retrieveProxy(AppConstants.START_ACTION).getData() as String;