Search found 157 matches
- Fri Dec 10 2021 8:11 pm
- Forum: Issues
- Topic: TLS connection using self signed certificates
- Replies: 3
- Views: 10972
Re: TLS connection using self signed certificates
Thank you for your interest in CopperSpice. We are using an updated network socket implementation which reports an error when a self signed certificate is used. By default this error will prevent the connection from being opened for enhanced security. If you want to allow self-signed certificates, y...
- Sat Sep 25 2021 5:20 pm
- Forum: Developers
- Topic: PDF library
- Replies: 4
- Views: 14161
Re: PDF library
It would be nice to see this library released under "LGPL 2 or later". I would consider it, but this line in your reply made everything you said seem invalid. To me and the wall LGPL 3 is "later" because 3 comes after 2. If the author wants a single license there are four distin...
- Thu Sep 16 2021 11:33 pm
- Forum: Developers
- Topic: QStringParser::toInteger<> bug
- Replies: 3
- Views: 12430
Re: QStringParser::toInteger<> bug
If it is a deliberate decision, then this is still a bug. The template code should be trapping char32_t specifically and delivering a meaningful message at compile time instead of letting the compiler generate close to 25 screens of attempts, exceeding scroll back buffers while offering zero inform...
- Sat Sep 11 2021 11:08 pm
- Forum: Developers
- Topic: QStringParser::toInteger<> bug
- Replies: 3
- Views: 12430
Re: QStringParser::toInteger<> bug
Looking at the docs on cppreference, it will seem like char32_t is an unsigned integer type. However, this is part of the documentation for C. To find the correct definition for char32_t, you need to make sure you are in the C++ documentation. In C++, char32_t is not actually a numeric type. It is a...
- Mon May 31 2021 12:25 am
- Forum: User Support
- Topic: Copper Spice on M1 Mac
- Replies: 22
- Views: 140697
Re: Copper Spice on M1 Mac
Thank you for your interest in CopperSpice. We appreciate your willingness to test this, it will benefit the project. As a first step, I would recommend you insert the following block before the #else in src/core/global/qglobal.h around line 89. #elif 1 #define Q_PROCESSOR_ARM 8 This will add a fall...
- Mon Apr 19 2021 5:13 pm
- Forum: Installation
- Topic: CopperSpice on arm target
- Replies: 7
- Views: 56641
Re: CopperSpice on arm target
This modification moved it forward ... #elif defined(__ARM_ARCH) # define Q_PROCESSOR_ARM 1 ... Thanks for looking at this and proposing a solution. The code you added assumes there is only one version of ARM, whereas there are many variants and they will all have to be accounted for. Based on the ...
- Sat Apr 10 2021 6:50 pm
- Forum: Issues
- Topic: QTextStream
- Replies: 1
- Views: 8322
Re: QTextStream
Given this bug first appeared in Qt 4.5 https://bugreports.qt.io/browse/QTBUG-12055 Did CopperSpice fix it? Hopefully, in their "spare" time, the CopperSpice developers are removing/fixing the "single threadedness" of Qt. Only being able to paint in the main event loop is a seve...
- Sat Apr 10 2021 5:30 pm
- Forum: Installation
- Topic: CsPaintDemo crashes
- Replies: 1
- Views: 32050
Re: CsPaintDemo crashes
Thanks for looking at CsPaint. We are currently not seeing these issues on any other system, and would like to investigate this further with you. Can you provide some additional debugging information? A description of the graphics hardware on your system (things like Integrated GPU, discrete GPU, dr...
- Fri Apr 02 2021 1:24 am
- Forum: Issues
- Topic: fromUnicode() documentation bug
- Replies: 3
- Views: 11452
Re: fromUnicode() documentation bug
The intent of the QTextCodec class is to convert between a QString and some specified text encoding. For Qt, the QString is in UCS-2, whereas for CopperSpice the QString is in UTF-8. In either case, the QByteArray that is returned by QTextCodec::fromUnicode will be in whatever encoding was requested...
- Fri Feb 19 2021 1:22 am
- Forum: Developers
- Topic: QStringParser::formatArg() for pointer
- Replies: 5
- Views: 14099
Re: QStringParser::formatArg() for pointer
It looks like you want a way to convert pointer to its string representation as a hex address. The simplest way to do this in CopperSpice is to convert the pointer into an unsigned integer of the appropriate size:
Code: Select all
QStringParser::formatArg( msg, reinterpret_cast<quintptr>(item), 0, 16);