CopperSpice Forum

CopperSpice 1.7.0 was released on September 7 2020 This release includes a full redesign of the QVariant class as well as XCB platform improvements, updates to SQLite and PostgreSQL, expanded API documentation, and lots of user reported modifications and improvements. For information about the chang...

The application failed to start because the platform plugin was not found or did not load. Requested Plugin Key: "cocoa" After you built KitchenSink did you run "ninja install"? During the install the required .dylib ( or .so or .dll ) file will be copied to your deploy/platform...

If most things are now wrappers for STL implementations Just to clarify, every container in CopperSpice was redesigned to wrap (using composition) an existing container in the STL. We also split up the QMap and QHash containers into four containers QMap, QMultimap, QHash, and QMultiHash. Using hand...

If there is an official bug database please let me know and I will put this there along with the malloc crash thing I reported earlier. We have noted your issues with QTemporaryFile and the malloc problem and someone on the CS development team will be reviewing them. Both items have been verified a...

Can you let us know what platform you are running on.

Thanks,

Barbara

Yes, you can call connect() and have the signal and slot both refer to a signal. This syntax is not valid: connect( sender, SIGNAL(someSignal()), this, SIGNAL(mySignal()) ); You can use this syntax: connect( sender, SIGNAL(someSignal()), this, SLOT(mySignal()) ); However we strongly suggest using me...

The class is actually called QLockFile. We will look at adding this to CopperSpice since it does appear to be of value.

Barbara

Signals must always be registered, so yes the CS macro registration syntax must be used. If you are passing the Slot as a string or using the SLOT() macro then you also need to register it. You do not need to register a Slot when a method pointer is used in the call to connect(). This is the preferr...

We do not set compiler options in CopperSpice. Developers should have the freedom to adjust these options for each project they are building. Some may want warnings on and others do not. It is not our position to force users to confirm to our settings. We use this same philosophy for building Diamon...

A solution for this issue was pushed to github. This required changing a CMake build file for FreeBSD systems.

sha 44b38f3

Barbara