General and Desktop

You already use QTextStream::readLine() - so why do you read it with ifstream before? You simply read it twice for no reason.

@vronin I guess I figured that by "onCompleted" they meant when the component was finished but apparently they were referring to the completion of the creation of the component? In any case, thank you!

Hi it means you should temporary pause it while user moves the Label to avoid the flashing. I assume " mouse move." means that user can select the label and move it around on screen. Also to make that look good, you should keep the offset into the WIdget where you "grab it" like they do there https://stackoverflow.com/questions/11172420/moving-object-with-mouse

Just an FYI, the order is also unspecified in C, but is fixed in left to right in Java

@aha_1980 #------------------------------------------------- Project created by QtCreator 2019-08-30T13:32:14 #------------------------------------------------- QT += core gui greaterThan(QT_MAJOR_VERSION, 4): QT += widgets TARGET = stlonly TEMPLATE = app The following define makes your compiler emit warnings if you use any feature of Qt which has been marked as deprecated (the exact warnings depend on your compiler). Please consult the documentation of the deprecated API in order to know how to port your code away from it. DEFINES += QT_DEPRECATED_WARNINGS You can also make your code fail to compile if you use deprecated APIs. In order to do so, uncomment the following line. You can also select to disable deprecated APIs only up to a certain version of Qt. #DEFINES += QT_DISABLE_DEPRECATED_BEFORE=0x060000 # disables all the APIs deprecated before Qt 6.0.0 CONFIG += c++11 SOURCES += main.cpp mainwindow.cpp stlfix.c HEADERS += ../pg/pgapi.h ../pg/pgkey.h ../pg/pgmacros.h ../pg/pgrender.h error.h mainwindow.h stlfix.h window.h FORMS += mainwindow.ui Default rules for deployment. qnx: target.path = /tmp/$${TARGET}/bin else: unix:!android: target.path = /opt/$${TARGET}/bin !isEmpty(target.path): INSTALLS += target INCLUDEPATH += C:\cygwin64\usr\include\X11 LIBS += C:\cygwin64\usr\include\ #INCLUDEPATH += C:\stlRepair_file #LIBS += -L/C:\stlRepair_file\lib\amd\winxp64\msoft14\dos_\ -lpg -lpgogl #INCLUDEPATH += C:\cygwin64\usr\include\X11 #LIBS += C:\cygwin64\usr\include #INCLUDEPATH += C:\cygwin64\usr\include #LIBS += C:\cygwin64\usr\include\ #INCLUDEPATH += -L\C:\stlRepair_file\bin #LIBS += -L/C:\stlRepair_file\lib\amd\winxp64\msoft14\dos_\ -lpg -lpgogl win32: LIBS += -L$$PWD/../lib/amd/winxp64/msoft14/dos_/ -lpg INCLUDEPATH += $$PWD/../ DEPENDPATH += $$PWD/../ win32: LIBS += -L$$PWD/../lib/amd/winxp64/msoft14/dos_/ -lpgogl INCLUDEPATH += $$PWD/../ DEPENDPATH += $$PWD/../ win32:CONFIG(release, debug|release): LIBS += -L$$PWD/../lib/amd/winxp64/msoft14/dos_/ -lpgogl else:win32:CONFIG(debug, debug|release): LIBS += -L$$PWD/../lib/amd/winxp64/msoft14/dos_/ -lpgogl INCLUDEPATH += $$PWD/../ DEPENDPATH += $$PWD/../ #win32: LIBS += -L\C:\Program Files (x86)\Windows Kits\10\Lib\10.0.18362.0\um\x64 -lBufferOverflow #INCLUDEPATH += C:\Program Files (x86)\Windows Kits\10\Lib\10.0.18362.0\um\x64 #LIBS += C:\Program Files (x86)\Windows Kits\10\Lib\10.0.18362.0\um\x64\ win32:CONFIG(release, debug|release): LIBS += -L$$PWD/'../../Program Files (x86)/Windows Kits/10/Lib/10.0.18362.0/um/x64/' -lBufferOverflowU else:win32:CONFIG(debug, debug|release): LIBS += -L$$PWD/'../../Program Files (x86)/Windows Kits/10/Lib/10.0.18362.0/um/x64/' -lBufferOverflowU INCLUDEPATH += $$PWD/'../../Program Files (x86)/Windows Kits' DEPENDPATH += $$PWD/'../../Program Files (x86)/Windows Kits' win32-g++:CONFIG(release, debug|release): PRE_TARGETDEPS += $$PWD/'../../Program Files (x86)/Windows Kits/10/Lib/10.0.18362.0/um/x64/libBufferOverflowU.a' else:win32-g++:CONFIG(debug, debug|release): PRE_TARGETDEPS += $$PWD/'../../Program Files (x86)/Windows Kits/10/Lib/10.0.18362.0/um/x64/libBufferOverflowU.a' else:win32:!win32-g++:CONFIG(release, debug|release): PRE_TARGETDEPS += $$PWD/'../../Program Files (x86)/Windows Kits/10/Lib/10.0.18362.0/um/x64/BufferOverflowU.lib' else:win32:!win32-g++:CONFIG(debug, debug|release): PRE_TARGETDEPS += $$PWD/'../../Program Files (x86)/Windows Kits/10/Lib/10.0.18362.0/um/x64/BufferOverflowU.lib' I think ,I have miss some step for linking.Please help

@meganathan said in QtConcurrent -thread not running concurrently: i tried setting the maxthreadCount to 8 but still only one executable is running out of 8, it is not running concurrently in Xeon processor machine. I am running the same executable in both the machine . Yes, in mapped function, i use Qprocess to launch and execute the console application I can think of 2 possibilities: Only 1 instance of the console application can be run at a time on the Xeon machine, OR There is an issue where Qt Concurrent can't use multiple threads in the Xeon machine To check (1), put debug messages at the start and end of your map function: QByteArray mapFunc(const QString& args) { qDebug() << "Starting " + args; QProcess p; // Do expensive task here qDebug() << "Finished " + args; } Do you see many "Starting" messages appear at the same time ("Starting" -> "Starting" -> "Starting" -> "Finished" -> "Finished" -> "Finished")? Or do you get a single-threaded sequence ("Starting" -> "Finished" -> "Starting" -> "Finished" -> "Starting" -> "Finished")? Also, how long does it take to run the console app? To check (2), upgrade to the latest version of Qt (I notice that you're still using Qt 4.8 which reached end-of-life in 2015). If the issue still exists in Qt 5.13, submit a report to https://bugreports.qt.io/

@minjunkim https://doc.qt.io/qt-5/qwidget.html#move-1

@sierdzio i just added this highlighted line into the main.cpp file and the output changed all of the text colours that were not attached to one of the stacked widgets pages that had layouts applied. So the ones without layouts changed the pages with remained the same.[image: a0a8da91-6d85-49a7-86c1-b54ceba6c406.png]

@alizadeh91 Basically, your question is the same as "How do I make a standalone executable that is compiled to native code that plays my animation." You need to either write or use a compiler and toolchain that builds software for the target. In this case, your target is webassembly rather than something like Win64 or OS-X. It's unclear if that's really what you want to do, but there's no real support for emitting webassembly from Qt, any more than there is for emitting Windows .exe's. Qt depends on the system's native compiler and toolchain to make compiled executables. It isn't a compiler in itself. If you are able to export your animations to a (de facto) standard format like Lottie : https://airbnb.io/lottie/ you can find off the shelf player tools which may be useful to you.

Hi, QRegExp is a custom regular expression implementation. QRegularExpression uses PCRE as a backend. Also, QRegExp should be considered deprecated and not used in new code.

stylesheet: "border: none" worked!! wow style sheets. wow. just... wow. that is amazing.