Jeff said: > I'm trying to understand why TargetManager creates some > actions like ActionAddAttibute but not other actions.
I think it's basically the actions which are used in the right-click context menu on the diagram that are managed in this way. They need to know if they're enabled or not based on the current target. Most other actions appear on property panels which are themselves listeners to the TargetManager, so all the context gets managed implicitly as part of choosing the current property panel. Bob said: > For ArgoUML having these instances owned by the TargetManager > simply saves the need for the listener mechanism. Possibly > they could be housed somewhere else with listeners too. Absolutely they should be split out. That's the whole point of the TargetManager as an independent service -- so everything doesn't turn into one big tangled ball of string. Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
