Search found 153 matches
- Mon May 31 2021 12:25 am
- Forum: User Support
- Topic: Copper Spice on M1 Mac
- Replies: 22
- Views: 29258
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: 13321
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: 4626
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: 7474
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: 6523
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: 7725
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);
- Wed Feb 17 2021 5:48 pm
- Forum: Developers
- Topic: Was there a change in QProcess::waitForReadyRead()?
- Replies: 3
- Views: 6710
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 readChannelFin...
- Mon Jan 18 2021 9:55 pm
- Forum: User Support
- Topic: Where's the UI Designer?
- Replies: 27
- Views: 102425
Re: Where's the UI Designer?
You should be doing all of your development on Linux. Most Linux distros have QtCreator in their repos; no registration required. Please be aware this does not reflect the opinion or the philosophy of the CopperSpice team or any of its members. We encourage users to develop applications on any of o...
- Thu Dec 24 2020 6:29 pm
- Forum: User Support
- Topic: GNU Assembler error building CsGui from 11.28 pull
- Replies: 6
- Views: 12602
Re: GNU Assembler error building CsGui from 11.28 pull
You have listed a couple of possible reasons the string table may be too big. The space available in the string table is limited to 10 MB in the windows object file format. Using a shorter path may help, as well as turning on some level of optimization to reduce the number of symbols and template in...
- Wed Dec 23 2020 5:58 pm
- Forum: User Support
- Topic: GNU Assembler error building CsGui from 11.28 pull
- Replies: 6
- Views: 12602
Re: GNU Assembler error building CsGui from 11.28 pull
Thanks for sending the additional information. Our "CopperSpice Overview" documentation for building on Windows MinGW uses MSys and not MSys2. I can confirm when building CsGui there are a few large files and you must enable "big object files" as we have done in our CMake files. ...