@SGaist Thanks, I looked into QSignalMapper, but it seems to have limitations, for example you can only pass one parameter and you can really just map one slot/signal. I could probably make it work by passing a structure (and register that with the meta compiler), and then use multiple QSignalMappers... but, at least for my case, I find that creating my own object to be much simpler both to implement and to read.

@SGaist Yes. That was intensional. I just tested that my installation is still providing the message. Thanks a lot anyway.

I figured it out. I needed to set my QObject and QCore stuff properly. In the .pro file of the shared library, I added: QT += core In the shared library's .h file, I switched this: class CTSCANSHARED_EXPORT ctScan { public: ...blah blah... with this: class CTSCANSHARED_EXPORT ctScan: public QObject { Q_OBJECT public: ...blah blah... And then ensured the shared library's .h file had this: #include <QObject> And then it compiled properly.

Hi, You can't pass a parameter when setting up the connection and since your using Qt 5 you should try the new connect syntax, it helps avoid that mistake. There also the possibility of using lambdas for such use case.

I would have expected that all Qt type are already registered. However, this is a template which you registered with template argument. That is presumably the reason. A template delivers infinite possibilities. I did not know.

@swegmann Yeah, it did the trick. Thanks

@Chris-Kawa Thank you very much!

@SGaist said: @sierdzio Indeed the back ticks are not mandatory, however it gives the forum engine a good hint of what is following in the cheat sheet you can actually find: Blocks of code are either fenced by lines with three back-ticks ```, or are indented with four spaces. I recommend only using the fenced code blocks -- they're easier and only they support syntax highlighting. The question is what is the syntax highlighting now?

Hi, Short answer: no The slot signature must either have the same number or less parameters than the signal and the type must be the same.

@jelicicm the exec() is typically called with a return at last position in main. Exec starts the event loop and continues until you quit the whole application. I recommend that you check out the example delivered with QtFtp This provides you a better start. When using Qt it is recommended to have a sound basis of C++. Your code looks as you are more familiar with C. It may help your understanding to go through some C++ tutorial, if you are not familiar with OOP and C++.