Comments on: Cairngorm Top 5 Tips – Number 5 – The AnnounceFaultEvent http://www.adamflater.net/2009/01/26/cairngorm-top-5-tips-number-5-the-announcefaultevent/ Tech, UX, Design Wed, 04 Jan 2012 21:31:56 +0000 hourly 1 http://wordpress.org/?v=3.5.1 By: Adam Flater http://www.adamflater.net/2009/01/26/cairngorm-top-5-tips-number-5-the-announcefaultevent/#comment-200 Adam Flater Tue, 27 Jan 2009 16:35:00 +0000 http://www.adamflater.net/?p=68#comment-200 Another point I didn’t think to mention… You can, of course, manually dispatch the AnnounceFaultEvent and add the specific data you’d like to use for the fault in question. In this scenario, some of your faults may just pass from Delegate to Command automatically, and some could be caught by the Command in a case-by-case scenario where the Command manually dispatches the AnnounceFaultEvent.

]]> By: Adam Flater http://www.adamflater.net/2009/01/26/cairngorm-top-5-tips-number-5-the-announcefaultevent/#comment-199 Adam Flater Tue, 27 Jan 2009 16:11:00 +0000 http://www.adamflater.net/?p=68#comment-199 Hi Andrew,

Glad you found value in the post. AnnounceFaultEvent is great for standard catch-all error handling. It sounds like your situation may be a bit unique. However, you may be able to add the window ID data on to the mx.rpc.Fault object that belongs to AnnounceFaultEvent. I’m not sure if it makes sense that your delegate would have that window ID reference, but at least this gives you a place to attach some data.

Cheers!
-adam

]]> By: Andrew Westberg http://www.adamflater.net/2009/01/26/cairngorm-top-5-tips-number-5-the-announcefaultevent/#comment-198 Andrew Westberg Tue, 27 Jan 2009 13:46:00 +0000 http://www.adamflater.net/?p=68#comment-198 Thanks for sharing this Adam. We’re using the UM extensions, but were unaware of this feature. I’m not sure we’ll be able to use this out of the box, however, since we have a multi-window AIR app that needs to pass additional information about which window should get the alert box popping up on it.

]]>