CopperSpice Forum

David, Thanks for your questions. I have downloaded the signals and slots from github. Just so we are on the same page, can you let us know what you downloaded? The ways I have tried get activate() Signal parameter mismatch. Please tell us what you are trying to implement and a sample of the code yo...

This macro was removed in favor of a using declaration. // Q_DECLARE_FLAGS(enumName, flagName) using flagName = QFlags<enumName>; // Q_DECLARE_FLAGS(Option, OptionFlags) using OptionFlags = QFlags<Option>; Thanks for letting us know about the documentation issue and please continue to tell us about ...

Here is an example to help explain how this works. The valueChanged() signal for QSpinBox has two overloads. When calling connect() using method pointers, the second parameter is a pointer to the signal and the fourth parameter is a pointer to the slot. If either the signal or the slot is overloaded...

We have uploaded a new CS Journal entry with a full working example and CMake build files. This example explains how to display a subset of the values in a QComboBox based on the text entered by the user in the line edit portion of the combo box. CopperSpice Journal - Gui Example 45 https://journal....

QComboBox currently has built in functionality to support these two items. (a) case sensitive/insensitive, the default is “case insensitive” (b) beginning of word match It sounds like you are interested in knowing how to use a QComboBox and have the display be limited by what the user has typed. We ...

I opened the "CopperSpiceLibraryTargets.cmake" file located in our Fedora 36 binary release (CS 1.9.1), dated Feb 19 2024. The binary distribution is located on our CS download page and also on our CS github page. We also tested CSMultimedia in KitchenSink using the Music Player and did no...

The single change has been made in our source code. It will be committed shortly.

Barbara

Thanks, we corrected the documentation. This will appear in the next release of the CS API documentation.

We have taken a look at your reported issue and we want to discuss what line 2 is really doing. Line 2 is taking a QVariantMap and storing it in a QVariant. If you call tmpVariant.typeName() it will return the data type of what the variant is storing. In this example code it is storing a QVariantMap...

Thank you for reporting this issues. We will add this as a unit test and make any changes which are required.