Search found 116 matches

by ansel
Sat Sep 25 2021 5:20 pm
Forum: Developers
Topic: PDF library
Replies: 4
Views: 380

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 distinct possibilities. Th...
by ansel
Thu Sep 16 2021 11:33 pm
Forum: Developers
Topic: QStringParser::toInteger<> bug
Replies: 3
Views: 2413

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...
by ansel
Sat Sep 11 2021 11:08 pm
Forum: Developers
Topic: QStringParser::toInteger<> bug
Replies: 3
Views: 2413

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...
by ansel
Mon May 31 2021 12:25 am
Forum: User Support
Topic: Copper Spice on M1 Mac
Replies: 9
Views: 3481

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...
by ansel
Mon Apr 19 2021 5:13 pm
Forum: Installation
Topic: CopperSpice on arm target
Replies: 7
Views: 3936

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 ...
by ansel
Sat Apr 10 2021 6:50 pm
Forum: Issues
Topic: QTextStream
Replies: 1
Views: 1367

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 severe flaw. As anyone o...
by ansel
Sat Apr 10 2021 5:30 pm
Forum: Installation
Topic: CsPaintDemo crashes
Replies: 1
Views: 1351

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...
by ansel
Fri Apr 02 2021 1:24 am
Forum: Issues
Topic: fromUnicode() documentation bug
Replies: 3
Views: 1890

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...
by ansel
Fri Feb 19 2021 1:22 am
Forum: Developers
Topic: QStringParser::formatArg() for pointer
Replies: 5
Views: 2767

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);
by ansel
Wed Feb 17 2021 5:48 pm
Forum: Developers
Topic: Was there a change in QProcess::waitForReadyRead()?
Replies: 3
Views: 2266

Re: Was there a change in QProcess::waitForReadyRead()?

In the API docs for readyRead() the signal is emitted "once every time new data is available for reading from the device." This signal does not indicate that all the data is available. If you want to know when the process has closed and all the data is available, connect the readChannelFinished() si...