General and Desktop

@Hamza-Umair Then why did you asked in the first place? And what's so hard to fill a bug report?

@Shriansh As already told you by @JonB you forgot to implement this function so the linker can not find it.

@Mesrine To deploy QtMultimedia in windows one has to pass -multimedia to windeployqt. From this, it says Since Qt 6.7, you can use DEPLOY_TOOL_OPTIONS to pass additional options to the underlying deployment tool. This only has an effect if the underlying deployment tool is either macdeployqt or windeployqt. This should deploy qtmultimedia and backends using the CMake API like qt_generate_deploy_qml_app_script( TARGET ${example} OUTPUT_SCRIPT deploy_script DEPLOY_TOOL_OPTIONS -multimedia ) install(SCRIPT ${deploy_script} COMPONENT examples) This will work for Windows but not for Macos. But one has to use some if the conditionals.

@Christian-Ehrlicher said in Problem with std::map management: @SamiV123 said in Problem with std::map management: just possibly non portable Which contradicts the c++ idea. Maybe so but that's not how real life works. In real life practically every C++ program is only as portable as the developers intended, i.e. it only compiles and runs on the platforms targeted by the developers.

See https://bugreports.qt.io/browse/QTBUG-90395

You could also look into using a style engine with SVG support. for example kvAntum.

@JacobNovitsky If you want to undo what you did then just do so. You did keep a backup, right?

@ymhsieh Although it may be better to create your own Material, we were able to display both sides of QPhongMaterial with the following code. // Material auto material = new Qt3DExtras::QPhongMaterial(rootEntity); auto cullFront = new Qt3DRender::QCullFace(); cullFront->setMode(Qt3DRender::QCullFace::NoCulling); for (auto tech : material->effect()->techniques()) { for (auto renderPass : tech->renderPasses()) { renderPass->renderStates().removeIf([=](Qt3DRender::QRenderState* renderState) { return dynamic_cast<Qt3DRender::QCullFace*>(renderState) != NULL; }); renderPass->addRenderState(cullFront); } }

@JacobNovitsky below seem to solve this task #!/bin/bash Set the directories containing the shared object files SPL_DIR="/home/j/SPL-Debug/debug/debug" SML_DIR="/home/j/SML-Debug/debug/debug" QPL_DIR="/home/j/QPL-Debug/debug/debug" Concatenate the directories with the current LD_LIBRARY_PATH export LD_LIBRARY_PATH="$SPL_DIR:$SML_DIR:$QPL_DIR:$LD_LIBRARY_PATH" Print the current LD_LIBRARY_PATH for verification echo "LD_LIBRARY_PATH is set to: $LD_LIBRARY_PATH" Use ldd to show the shared libraries used by the QUI application ldd /home/j/QUI-Debug/QUI

@JonB Thanks for your awesome reply. I think you are right. It only causes a problem (in the original example) if in on_pushButton_2_clicked the code calls setRange first and then call setTickInterval because (apparently) only setRange calls calcuilateLayout as you determined. I have submitted a bug report to Qt (QTBUG-124158). For now, I will mark this forum topic as 'solved' and then after the QTBUG is resolved I will come back to this forum topic and update it.

It was possible to obtain it via the QGeometryView class like planeMesh->view()->geometry().

@Pl45m4 yup that's the one. much appreciated

Hi, Use the same QNAM, however rather than connecting its finished signal, do it for the reply of your request so you can properly handle the two request independently.

@jsulm True. Thanks.

@Ronel_qtmaster Thank you very much. The project has been successfully opened!

@GrecKo https://stackoverflow.com/questions/45563393/sort-the-data-of-a-qml-listview-by-using-a-qsortfilterproxymodel https://github.com/oKcerG/SortFilterProxyModel/ OIC you were the replier & author :)

@kuzulis Because that's exactly what this virtual function is for. In QIODevice it says "This function can operate without an event loop. It is useful when writing non-GUI applications and when performing I/O operations in a non-GUI thread." So the latter part sounds exactly like what i did... I don't see why that would be bad design? Telling one not to use a function which is clearly meant to be used in a thread and completely ignoring the constraint to have a synchronous snippet/ a single function is just misleading at best.

Given that screens refresh with 50 or 100 Hertz, microsecond update rates are useless. I'd use a QTimer with an resolutio of 10 milliseconds, for example. Then draw a bunch of points at once. That should give the best performance. Regards

And I've now tried the Qt 6.7 CAN Manager example with PCAN-Basic 4.8.2.897. Sending and receiving works like a charm. @NoobyLost Do you have an event loop running?