CopperSpice Forum

The missing method has been pushed to github. Thanks for reporting this.

Thanks for the request. The new class has been pushed to github.

I read your private message and we understand you expressed limited experience with CMake and debugging. I would like to mention that debugging is a learned skill. It sounds like you have been able to make good progress in tracking down this issue. You also mentioned wanting to learn more about debu...

Thank you so much for doing a great deal of debugging and producing such a small test case. I have downloaded your samples and we will take a look at reproducing the issue you are seeing. We knew Mint was similar to Ubuntu, however a year ago someone had some obscure incompatibilities but were never...

The connect method in Qt using the SIGNAL and SLOT macros simply ignored qualifiers like const which can hide problems. We disagree with this approach and feel it is misleading. When we designed the CopperSpice registration system and removed moc, we were careful to preserve the exact data types thr...

Thanks for reporting this. Can you give us a very short test case which shows only the links you expect to work? Also, a copy of the project file that you are using will help us diagnose what is happening.

When across threads are they queued automatically like in Qt? If I understand your question correctly, you are asking about the behavior when the sender and receiver belong to different threads. We can not confirm that this actually works in Qt, as we observed some undefined behavior in the signal/...

The code in Diamond is correct. You may not be aware that there are multiple overloads of the connect() method. We have added a note to our CopperSpice Overview documentation to indicate slots only need to be registered if they are used with the string overload of connect(). Since Diamond uses metho...

I was not able to find either this crash or the error you are reporting when running on my Debian 10 machine. I will set up a ubuntu 16 VM and see if I can reproduce it there.

Thanks for your interest in CopperSpice. The exact requirements for a successful build will of course vary depending on your platform and compiler. In general a Linux build system needs at least 8GB of RAM plus 12 more of swap to link successfully. We plan for roughly 3 GB per compile process (-jN) ...