General and Desktop

Using 64K combos from 2bytes, with 2 decimal points zero to 640.00+ appears possible. The point is not decimal. 10 bits of fractional gives you 3 decimal digits, meaning that you get 6 more bits for the leading part, which is 64 (in decimal), so 64.xxx is exactly representable. You could "lie" if you can settle to give up a bit from the fractional part: 7 bits leading + 9 bits fractional -> up to 128.xxx with 2.7 decimal digits after the dot (your LSB in decimal would be 0.002 then)

Fixed, no longer an issue. QRect rctSection; int intOnscreenSpan((truth::msintViewMax - truth::msintViewMin) * mptPixelsPerBSCAN.y()), intYoffset(truth::msintViewMin * mptPixelsPerBSCAN.y()); intYoffset = intOnscreenSpan + intYoffset; rctSection.setRect(0, rctOffscreen.height() - intYoffset, mszOnScreen.width(), intOnscreenSpan); QImage imgSection(imgStrip.copy(rctSection));

Here is one approach you could find with 30 seconds of looking in the examples: https://doc.qt.io/qt-5/qtwidgets-richtext-orderform-example.html

@eyllanesc thank you,i will try it.

"`" QSurfaceFormat surfaceFormat; surfaceFormat.setMajorVersion(4); surfaceFormat.setMinorVersion(3); QOpenGLContext openGLContext; openGLContext.setFormat(surfaceFormat); openGLContext.create(); QOffscreenSurface surface; surface.setFormat(surfaceFormat); surface.create(); openGLContext.makeCurrent(&surface); QOpenGLFunctions *f = openGLContext.currentContext()->functions(); f->initializeOpenGLFunctions(); f->glFlush(); QSize vpSize = QSize(m_ScreenWidth, m_ScreenHeight); qDebug("Hi"); QOpenGLFramebufferObjectFormat fboFormat; fboFormat.setAttachment(QOpenGLFramebufferObject::CombinedDepthStencil); m_fbo = new QOpenGLFramebufferObject (vpSize, fboFormat); fboFormat.setTextureTarget(GL_TEXTURE_2D); RenderAllOPenGLWidgets(); // reendering all widgets based on timestamp. this->update(); QCoreApplication::processEvents(); QThread::usleep(1000); m_fbo->release(); QString ImageName = QString::number(FBOCaptureTime) + QString(".png");; QImage fb = m_fbo->toImage().convertToFormat(QImage::Format_RGB32); fb.save(ImageName, "PNG"); "`"

@Abhi_Varma said in QByteArray dequeue() crash: @SGaist Yes. It is multithreaded app. and how can I protect the access to the queue. If you're unsure about this, maybe you shouldn't do multi threading to start with, especially as Qt-Classes/Modules have almost always asynchronous apis. For completeness however take a look at mutexes https://doc.qt.io/qt-5/qmutex.html https://en.cppreference.com/w/cpp/thread/mutex (I have added few more comments to the post at the end) My question why isn't my exception handling working and how can I resolve this. because c++ is not js or python, you can't move everything in a try catch block and be done with it. That only works when exceptions are actually thrown. 😉 An invalid pointer/instance access does not fall in that category :D

Hi, and welcome! @Victor-Dai said in Undefined symbols for architecture x86_64:: /usr/local/lib/libhiredis.dylib, building for macOS-x86_64 but attempting to link with file built for macOS-arm64 You are using an x86_64 compiler but you are trying to link to an ARM64 library. That is not allowed. Some possible solutions are: Install an x86_64 version of libhiredis, OR Wait for Qt 6.2 to be released, and then build your application with an ARM64 compiler: https://bugreports.qt.io/browse/QTBUG-85279

Hi, thanks for the answer, it works perfectly :D

@SPlatten said in QString % symbol: "height:%1%2;}").arg(dblPercentOnView).arg("%")); For a literal % you should find QString accepts %%, so I would find simpler/more readable "height:%1%%;}").arg(dblPercentOnView));`

Hi, When testing for an error, it's usually a good idea to at least print that something went wrong and not just exit early like you do in your constructor.

I reinstalled Qt, the issue disappeared but now I'm having the commercial version of Qt ??!!?? Fixed this last issue by creating a new Qt account. Please Qt Company, fix your installer.

@mrjj Well… If I end up capturing an HID device exclusively, using native code, then it shouldn't cost much. Using an arduino-ish needs an arduino and a USB host on this device to make it a serial port. For now, I think costs would be equivalent (no device but more time using native code, device but less time using QSerialPort. Thanks for your input

@sierdzio Thank you.

still in mingw way problem not solved . so i choose msvc compiler to do that .. so iam closing this ...

@Cobra91151 No worries, I saw that you deleted the dialog at the end of the method. Just pointing out that it's an easy to forget step and that in this case it was not necessary to use the heap for that. It's also one small thing that allows for reduced heap fragmentation.