summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAkarsh Simha <akarsh@kde.org>2016-08-17 21:59:42 (GMT)
committerAkarsh Simha <akarsh@kde.org>2016-08-18 08:47:59 (GMT)
commit52d368d09c896b6a1cab32e46b2fb06935b9fdd2 (patch)
treef4b36de5e836bbf736516bfc38d04255794bd885
parentd8442c5a55f9771c209a1e1f05c078e7ae1c71a2 (diff)
Update a comment...
... with things that were discovered the hard way.
-rw-r--r--kstars/tools/observinglist.cpp4
1 files changed, 3 insertions, 1 deletions
diff --git a/kstars/tools/observinglist.cpp b/kstars/tools/observinglist.cpp
index 7a98f80..e6aa7ef 100644
--- a/kstars/tools/observinglist.cpp
+++ b/kstars/tools/observinglist.cpp
@@ -1282,7 +1282,9 @@ void ObservingList::setSaveImagesButton() {
// FIXME: Is there a reason to implement these as an event filter,
// instead of as a signal-slot connection? Shouldn't we just use slots
// to subscribe to various events from the Table / Session view?
-
+//
+// NOTE: ui->ImagePreview is a QLabel, which has no clicked() event or
+// public mouseReleaseEvent(), so eventFilter makes sense.
bool ObservingList::eventFilter( QObject *obj, QEvent *event ) {
if( obj == ui->ImagePreview ) {
if( event->type() == QEvent::MouseButtonRelease ) {