I figured it out. Interestingly, cmake was not selected on the Qt installer by default. I had to install cmake through the Qt Maintenance Tool and then select the cmake version on the Qt6.8.3 default kit. I find it very strange that it was not installed by default. Tricky tricky...

image.png

What are you trying to achieve? from what it looks in your setupUI() function you don't use Ui::Dialog at all.

The full example code can be found here (as written in the documentation): https://code.qt.io/cgit/qt/qtbase.git/tree/examples/corelib/ipc/sharedmemory?h=5.15

P.S. an idea how to get the config to active the Qt Wayland driver for raspberry pi? Or does it do this only when building the target qt targeted at the pi? I can't find any documentation about put what option to put into configure or qt-configure-module it pure luck of finding a forum post and looking at others options so if anyone has any documentation for this it would be great.

Qt Wayland Drivers: EGL .................................... yes Raspberry Pi ........................... no

@Yuyang I suggest you upgrade your QtCreator and MinGW versions, because you're using quite old versions.

There's no stack trace as my application hasn't crashed.

The Application Output shows:
ASSERT failure in QList::operator[]: "index out of range", file /home/jsm/Qt/6.8.3/gcc_64/include/QtCore/qlist.h, line 458

I click ok, then Step, then the message pops up again. (As expressions are evaluated on each step.)
Neither QtCreator nor my application terminate. (My post title is slightly misleading, it isn't a full crash.)

James

I can do below with push for now and seems to be working, but I would like to have strong type checking nature of pushItem.

stackView.push(item, undefined, StackView.Immediate);

@unknown_error
I do not use Windows/MSVC/CDB so cannot answer any deeper than this, but it is a "first chance exception". That is an MSVC debugger thing and should be ignored --- you are not interested in any first chance exceptions which occur. Try unchecking that First chance exceptions checkbox? Does the debugger actually stop at that breakpoint? In which case you will just have to continue from there. I do not know if you can permanently ignore it.

Type the following into deepseek or grok, you may be able to find some clues.

Before hot plug, the push button click can receive events. But long press touch screen and hot plug touch board（at the same time. qt app(push button) cannot receive mousepress event, button click not work

@jsulm But why did it work on linux, the same code tho.

@exactchange
First: stop insulting others! Read and follow https://forum.qt.io/topic/113070/qt-code-of-conduct Unless you want to be banned from here.
Second: this is user forum, most people here are not from QtCompany and don't spam you - why are you insulting them?

If you want to be constructive you should at least mention what kind of mails you get, so that somebody can figure out from where it is coming and how to stop it.

I overlooked the portion of the request to separate the index change from the delegate. The current index can be pulled from the view's currentRow and currentColumn properties, or from the selection model. Eg view.selectionModel.currentIndex.row and view.selectionModel.currentIndex.column.

@DalePennington worker is an object. Connect worker with any widget or object which sends signals to worker.

@Vishal-Biradar I don't know what tool is not found and why. Seems to be "Renesas Flash Programmer", but I don't know why it is not found. Maybe it needs to be installed and added to PATH?