I do not know but this is really not a problem to have a event group class we can discarded in no time. So I would not bother with it. On Dec 11, 2011, at 8:07 AM, Igor Stasenko wrote:
On 10 December 2011 10:41, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
I would not say useless may be you need the composite and you do not need to repeat AddChild, RemoveChild all the times but use the composite
well.. usually a different events suppose different reactions to them, otherwise why care making lot event kinds if you handle them similarily?
Igor Stasenko wrote
which is pretty useless IMO.
The collaborative book says:
If you want to register the same action for multiple events, simply create an AnnouncementSet using a comma:
Parent>>initialize super initialize. self session announcer on: AddChild, RemoveChild do: [:it | self changeChild: it child]
-- View this message in context: http://forum.world.st/Re-Pharo-users-COTDC-94-AnnouncementSet-tp4178427p4179... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
-- Best regards, Igor Stasenko.