This activity doesn't support startup cancellation: super.start() will
view.setDelegate() (among other things) whether or not the activity was
It will be a real problem in the case you switch from a FindAndEditProxy
(FAEP) to a CreateAndEditProxy (CAEP), if they share the same singleton
1. FAEP starts (async)
2. user changes his mind: FAEP is cancelled (a no-op actually) and CAEP
is started (synchronous: sets itself as the view delegate)
3. FAEP async start response arrives: calls super.start which
overwrites the view's delegate.
From the ActivityManager POV, FAEP is dead and CAEP is active, but
actually the view delegates its events to FAEP, and CAEP is "blind"
(kind of a zombie activity).