@jsulm Fortunately, I just solved it. I should not have specified the VerticalWidgetList class as the parent of the widgets added. Apparently, when you add it to the layout, the widgets added get some sort of other parent class. I still nullptr out the widget in the takeWidget() function, however, as control of it should pass to the function receiving the return value. When I got rid of setting the parent in the addWidget() and insertWidget() functions, it now works properly.

I do wonder if I should still delete the child widget in removeWidget() and removeWidgetAt() after removing it from the layout. Or do I need to set the parent to nullptr before deleting it? When my program used clearWidgets(), which calls removeWidget(), there was no problem.

It works now!

This is the source code now:

verticalwidgetlist.h

#ifndef VERTICALWIDGETLIST_H #define VERTICALWIDGETLIST_H #include <QScrollArea> #include <QVBoxLayout> #include <QWidgetList> class VerticalWidgetList : public QScrollArea { Q_OBJECT public: explicit VerticalWidgetList(QWidget *parent = nullptr); bool addWidget(QWidget *child); void clearWidgets(); bool insertWidget(int index, QWidget *child); bool removeWidget(QWidget *child; bool removeWidgetAt(int index); QWidget *takeWidget(int index); int widgetAt(QWidget *child) const; private: QWidget *m_central; QVBoxLayout *m_layout; QWidgetList m_list; }; #endif // VERTICALWIDGETLIST_H

verticalwidgetlist.cpp

#include "verticalwidgetlist.h" VerticalWidgetList::VerticalWidgetList(QWidget *parent) : QScrollArea(parent) , m_central(new QWidget) , m_layout(new QVBoxLayout(m_central)) , m_list() { setWidget(m_central); setWidgetResizable(true); } bool VerticalWidgetList::addWidget(QWidget *child) { if(child == nullptr) return false; m_layout->addWidget(child); m_list.append(child); return true; } void VerticalWidgetList::clearWidgets() { while(m_list.count()) { QWidget *widget = m_list[0]; removeWidget(widget); } } bool VerticalWidgetList::insertWidget(int index, QWidget *child) { if(index < 0 || index > m_list.count()) return false; if(child == nullptr) return false; m_layout->insertWidget(index, child); m_list.insert(index, child); return true; } bool VerticalWidgetList::removeWidget(QWidget *child) { if(child == nullptr) return false; m_layout->removeWidget(child); int index = widgetAt(child); m_list.removeAt(index); delete child; return true; } bool VerticalWidgetList::removeWidgetAt(int index) { if(index < 0 || index >= m_list.count()) return false; QWidget *widget = m_list.takeAt(index); m_layout->removeWidget(widget); delete widget; return true; } QWidget *VerticalWidgetList::takeWidget(int index) { if(index < 0 || index >= m_list.count()) return nullptr; QWidget *widget = m_list.takeAt(index); m_layout->removeWidget(widget); widget->setParent(nullptr); return widget; } int VerticalWidgetList::widgetAt(QWidget *child) const { if(child == nullptr) return -1; return m_list.indexOf(child); }

EDIT: If anyone tried the source code up until this point, in this post, try again. I was rearranging removeWidget() and removeWidgetAt(), which I realized were mismatched in terms of their parameters. It's good now!

@Jokerking
Well which part ?

It loops over the full area , minus the area used for scrollbar

for r (float i = 0; i < widthMinusScrollbars; i += tickSize, tickCount++) {

It advances ticksize pr loop

every 5 tick count

size_t length = tickCount % 5 ? shortTickLength : longTickLength;

it shows a long tick.

then at every 10 tick ( i think) it draws the some text.
Has a bug there as
value = i * *tickSize / ratio;
seems very odd to me.

Then it draw some image.

@Chris-Kawa ah ok that worked and learned something new thanks

@TUStudi
I do believe this is the neater way to go. Your MainWindow and your TestClass are now quite independent of each other. If you had done "call a slot from MainWindow directly" TestClass would not be (re-)usable without MainWindow.

Your BluetoothController should have a member variable of the BluetoothModel class.
Your BluetoothModel class should provide an API that your BluetoothController can connect to and also that provides whatever data is needed.

@mrjj Thanks for the newline example, but yeah, I am planning for some other requirements (coloring, custom arrangements, no-columns etc.)

@Christian-Ehrlicher , Thank you for your help. I finally resolve the issue by removing the shared pointer for the label.

@Chris-Kawa
Thank you, this solves the problem. As to alternative way to exit, I already have exit action on tray's menu.
Have a nice day.

Same problem here with QPushButton's menu.
Qt 5.14.1, Mingw, Windows 10, Windows 11.

and some interest thing is that when I use an application to record my screen, it's showing the menu!!!!!! (checked the video of screen), but I can't see when interacting :|

@TMJJ001 said in C++ application with QML UI:

I created a widget application.

Create a QML application instead. You will write your UI with QML/QtQuick and logic in C++.
See https://doc.qt.io/qt-5/qtqml-cppintegration-topic.html

Vielen Dank @J-Hilk für den Link zur sehr guten Dokumentation was mir weitergeholfen hat.

Vielen Dank auch an @mrjj der auch einen entscheidenen Tipp gegeben hat eben dass es nur mit dem MSVC Compiler funktioniert. Habe beim Installationsprozess von "webengine" auf der rechte Seite gesehen das MSVC 2017 erforderlich ist von daher stimmt die Aussage absolut.

Vielen Vielen Dank nochmals an euch beiden die mir geholfen haben.

Grüße
Sven

Do you mean that the UI should be responsive and the user could do something useful while the widgets are generated and shown one by one? You can probably use a zero timer signal and a slot for that. In this way everything happens in the same thread but the signals created by user interactions are handled between timer signals.

@raven-worx Thanks, I will try that. I let you know if it works or not.

Hi and welcome to devnet,

You should define what you mean by better looking maybe post an example of what you are after.

Implementing your own style might also be an option.

Twój Rectangle jest root objektem w strukturze QMLa, więc nie ma rodzica - to normalne.

Albo użyj QMLa do całego swojego GUI, albo dodaj objekty, których potrzebujesz do contextProperty w silniku QML.

Apparently it is virtually impossible to do what I want because the QTextBlock itself hardcodes a QTextLayout in its ::layout() method (see here). Moreover, it seems that every hook we could use is only available in the private classes...

Now, the problem is that it prevents everybody wanting to implement custom behavior to create anything based on the QTextDocument and its associates. I wonder how the people who created text editors got away with this (probably implemented everything from scratch).

Well, at the end, the only thing I found that could work was to manually insert unicode U+002028 (Line Separator) wherever I want using QTextCursor, which is terrible because everytime the editor area width changes I have to remove the old ones and insert new ones...

As I'm not happy with the solution I found, I'll not mark this question as solved.

@SGaist

I found the solution in the mplayer's docs, the -wid not working in linuxfb environment. The qprocess started the mplayer who writes the framebuffer directly, it's working.

Hi
the include in the ui_ comes from
QString WorldTimeClockPlugin::includeFile() const
{
return QStringLiteral("worldtimeclock.h");
}

but it seems the error contains no filename ??