General and Desktop

@nicker-player said in what should i do to disable the qDebug() method on the release version?: DEFINES += QT_NO_WARNNING_OUTPUT This is misspelled (you should always look things up and copy+paste not type, especially if English is not your native language), so if you are getting a warning it might be why? If there are qDebug() statements in Qt code rather than explicitly in your own, #define will make no difference. I do not know whether Qt's own Release libraries are are compiled with QT_NO_DEBUG_OUTPUT or not. Correct the spelling and see where that gets you.

I found marknote, I see that the performance is fine, but I don't understand why, the logic in general is very similar

Alright! it's all working thank you very much for your help. I've got my app being distributed with both the wayland and xcb files. I'm copying both libQt6WaylandEglClientHwIntegration.so.6 and libQt6WaylandClient.so.6 into my core Qt\libs\ dir. as well as the wayland-decoration-client, wayland-graphics-integration-client and wayland-shell-integration dirs into my Qt folder too. I thin it was the missing integration folders that was causing me to have problems earlier on. Thanks for you help everyone, and hopefully this can assist someone in the future. James

@dextermagnific Yes, I have realized that, but installing python3-pyside6 through dnf in fedora kde spin seem to cause it to not boot, and I'd have to update all packages from a hooked up tty for it to boot. I'm going to make a reproducer with this issue when I'm less busy and probably talk on the fedora forums to see what they've got to say about this.

@SGaist Thank you for replying! I found the problem. I had a problem importing VTK-related dependency libraries. After I re-imported the related libraries, the function returned to normal.✌️

@Mitchal-Dichter said in Is there a simple way to make a triangle in Qt3D?: working directly with Direct3D, Metal, and Vulkan and skipping Qt Even though this is a Qt Forum here and Qt is in fact a great framework, sometimes you better look for something else. In your case, if you plan to render everything directly, you could also pick an immediate GUI, like ImGUI together with a Vulkan (on mac through MoltenVK), D3D or OpenGL backend. Fee free to post some updates on this or showcase your approach later :)

Thank you I'll go the inotify way. I just need to check that "commits" to the settings file are atomic so I won't be reading garbage (I read somewhere that QSettings handles well that).

i got it event->modifiers() & Qt::ShiftModifier

You may wish to download the source code for DeepSkyStacker 5.1.0 which was first released step in the journey from MFC to Qt (5.1.0 is a hybrid). You can DL the source code from here: https://github.com/deepskystacker/DSS/archive/refs/tags/5.1.0.zip. The file of interest is DeepSkyStacker\DeepSkyStacker.cpp HtH David

@The-Force said in QT 5.15 Windows Crash on deallocation of QModelIndexList: __acrt_first_block == header ...usually points at out-of-bounds access. if (!list.empty() || ui->classList->model()->rowCount() == 0) ui->shipCombo->setCurrentIndex(list.first().row()); If list is empty and the model's row count is zero, list.first() causes a read out of bounds and is probably the reason for the crash. Something like if (!list.empty() && ui->classList->model()->rowCount() != 0) ui->shipCombo->setCurrentIndex(list.first().row()); ...would make more sense to me.

@SGaist 6.9.1 + vs2022

@schrute What I found to be effective, is to leave it as a bordered window, and just intercept the WM_NCCALCSIZE message, so that it does nothing. This basically gives you a bordered window, where you stop windows from drawing the borders. This way, when you implement your own title bar, aero snap will still work.

I will not look at qml but maybe it's a good starting point for others who want to debug this.

I found these Natvis visualizers to be working fine with Visual Studio Code, if that helps you: https://github.com/narnaud/natvis4qt/tree/main/natvis QJson value visualizers are only included in the qt6.natvis file.

I fixed this issue. It was a Qt 6.9.0 bug, but Qt 6.9.1 has the fix

@jawadulhassan Hi Thank you for the hint, the setModal(true) and setWindowModality(Qt::ApplicationModal) has no effect. the activateWindow() where do you mean I should locate it? If I see it right, the opening of the editor is done in the QAbstractItemView. Do you have a sample which fixes this issue?

The solution is qt6-help-devel

Thank you, I'll have a look at its code to mimic its behavior.

Hi and welcome to devnet, Shouldn't you set the radius on the drop-down as well ? See the QComboBox example in the stylesheet documentation.