de16108dff
Previously, when you clicked on a notification, it would call this.source.clicked(), which would emit a 'clicked' signal on the source, and then various other stuff would happen from there. This used to make a little bit of sense, when clicking on a notification was supposed to do the same thing as clicking on its source, but makes less sense now, when clicking on the source itself *doesn't* call source.clicked()... Change it so that when you click on a notification, the notification emits 'clicked' itself, and the source notices that and calls its notificationClicked() method, and the various source subclasses do what they need to do with that, and Source no longer has a clicked method/signal. https://bugzilla.gnome.org/show_bug.cgi?id=631042
GNOME Shell provides core user interface functions for the GNOME 3 desktop, like switching to windows and launching applications. GNOME Shell takes advantage of the capabilities of modern graphics hardware and introduces innovative user interface concepts to provide a visually attractive and easy to use experience. For more information about GNOME Shell, including instructions on how to build GNOME Shell from source and how to get involved with the project, see: http://live.gnome.org/GnomeShell Bugs should be reported at http://bugzilla.gnome.org against the 'gnome-shell' product. License ======= GNOME Shell is distributed under the terms of the GNU General Public License, version 2 or later. See the COPYING file for details.