Signals must now be published under specific topics using EventAdmin.

Libs/PluginFramework/service/event/ctkEventAdmin.h

@@ -76,17 +76,12 @@ struct ctkEventAdmin
    * it under multiple topics. In that case, emitting the signal will result in
    * multiple events being send.
    *
-   * If the <code>topic</code> string is empty, a <code>std::invalid_argument</code>
-   * exception will be thrown.
-   *
    * @param publisher The owner of the signal.
    * @param signal The signal in normalized form.
    * @param topic The event topic to use.
    * @param type Qt::QueuedConnection for asynchronous delivery and
    *        Qt::DirectConnection for synchronous delivery.
    *
-   * @throws std::invalid_argument If <code>topic</code> is empty.
-   *
    * @see unpublishSignal()
    */
   virtual void publishSignal(const QObject* publisher, const char* signal,

Plugins/org.commontk.eventadmin/dispatch/ctkEASignalPublisher_p.h

@@ -40,7 +40,8 @@ public:
   QString getSignalName() const;
   QString getTopicName() const;
 
-protected Q_SLOTS:
+  QString getSignalName() const;
+  QString getTopicName() const;
 
   void publishSyncSignal(const ctkDictionary& eventProps);
   void publishAsyncSignal(const ctkDictionary& eventProps);