Yeah, you pretty much need to track those Connection objects
![Confused :?](./images/smilies/icon_confused.gif)
The internals of it are that each subscription to an event creates a new internal 'subscriber' object; the only external way to control that is via the returned Connection.
Since you're obviously after something a little more advanced, you might consider sub-classing the types you're targetting and setting up something custom built via the Windows on<event> handlers (which you could code in such a way to enable quick and easy connections right across all instances of the type). If you register a factory for your subclasses and alias them to the 'normal' type (for example Taharez/Button), then whenever a widget of that type is requested, they'd actually get your sub-class.
Not sure if that's explained very well, but I hope so
CE.