Hello, I found that subscribers handle announcements in order differ then order in which they subscribe. Reason - announcer subscriptions is dictionary. Maybe dependency of announcement handling order is bad code design. But it can be usefull.
Example. I need announcerA delegates announcements from another announcerB. And I need announcerA handles some specific announcement for own task. I try this code: announcerB on: SpecificEvent send: #specificHandler: to: announcerA. announcerB on: Announcement send: #announce: to: announcerA I want announcerA handles SpecificEvent (by #specificHandler) before other subscribers to announcerA .With current announcements implementation this code not work. What you think about this? I see announcer implementation. And I dont found some reason for dictionary subscriptions. Maybe we can fix it.
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
