it works fine except for browser url changes, which trigger a SWFAddressEvent.CHANGE event, which in turn causes a notification to be sent.
Its a typical chicken & egg problem, the notification is sent BEFORE the view mediators have been registered.
Then either:
A) Don't register the SWFAddressProxy until after the view has been prepared,
B) Use a Mediator instead of a Proxy to interface with SWFAddress
What is the best way to handle proxy to proxy communication?
Depending on your situation:
1) Proxy A retrieves Proxy B, invokes methods and sets properties on it. They are both registered during normal startup.
2) Proxy A creates Proxy B when needed, and maintains a reference to it so that it can invoke methods and set properties on it when needed.
Cheers,
-=Cliff>