Usually things like that are done using the "EventBus"-Pattern. I don't know the
Qt-Plugin-System, so I'm not sure if it is applicable for you...
It usually works like this:
- You have an "EventBus"-object in your application (not in the plugins!) which
is a singleton, so only one instance is crea
n
> Sent: Tuesday, May 27, 2014 9:41 AM
> To: Interest@qt-project.org
> Subject: [Interest] Design of 'pluginable' application
>
> Hi
> I am designing an application built around plugins.
> I know how to create plugins and read them in at run time, but now I
>
> -Original Message-
> From: interest-bounces+kai.koehne=digia@qt-project.org
> [mailto:interest-bounces+kai.koehne=digia@qt-project.org] On Behalf
> Of Graham Labdon
> Sent: Tuesday, May 27, 2014 9:41 AM
> To: Interest@qt-project.org
> Subject: [Interest]
Hi
I am designing an application built around plugins.
I know how to create plugins and read them in at run time, but now I need a way
of invoking the signal/slot mechanism between them.
For example, in a simple scenario I have plugin1 that has a slot for processing
a signal the plugin2 emits.
Pl
