On Sun, 10 Apr 2011 15:28:31 +1200, Joseph Groover <looncraz@xxxxxxxxxxx> wrote:
Why are listeners managed per decorator? Seems they would be managed per Desktop, and perhaps events would be handed down if need be. I haven't checked to see if they are used anywhere by the decorators, but I'll be getting there.
At the moment the listener belong to a decorator. I introduced it for Stack & Tile to load S&T by switching the decorator. The S&T logic lives in the desktop listener. Because of that, when changing the decorator all listener of the old decorator have to unregistered and the new one have to be registered. For a switch from S&T to the default decorator this would simply mean to unload S&T, the default decorator does not have any listener so nothing will be registered.
For now, I am preparing the following patches for proposal: A DecorInfo implementation & accompanying resource-based decorator information protocol.Single loaded add-on in DecoratorManager + DefaultAddOn at any given time.
what do you mean by single loaded?
Never-mind people. DesktopListener is kind of a poorly descriptive name ( more like a WindowEventListener ), but it makes sense now.
it listen for events in the desktop not necessarily window events...
Regards,
Clemens
