@vicky_mac A QStackedWidget works like a book. You have pages with your content. You can flip these pages to change your widget inplace (without opening another window or something else). So one possibility is to put one of each QTabWidget (each with a different tabBar position) on a page of a QStackedWidget. You could flip the pages by clicking a dummy tab on each tabBar or you use a button to go to the next page. I know, this is not exactly what the widget in your image looks like :) @vicky_mac said in How to Add multiple Qtoolbar in QtabWidget: Haven't used QT much If you want a widget, that looks exactly like the one shown above, you could still try to subclass and create your own, custom TabWidget, but I fear, that it might be a little too challenging. Here's all you need to know about QStackedWidget (https://doc.qt.io/qt-5/qstackedwidget.html#details)

Hi As far as I know, there is nothing like that in Qt. It can blur widgets but not the actual desktop.

UPD: I write this method for drawing, looks good { QLabel::paintEvent(event); QPainter painter (this); painter.setPen(Qt::green); painter.setBrush(palette().windowText()); painter.setRenderHints(QPainter::Antialiasing | QPainter::TextAntialiasing); painter.setFont(font()); QRect font_rect = painter.fontMetrics().boundingRect(text()); QRect label_rect = contentsRect(); label_rect.adjust(margin(), margin(), -margin(), -margin()); int dx = label_rect.width() - font_rect.width(); int dy = label_rect.height() - font_rect.height(); int x = 0; int y = 0; if (alignment() & Qt::AlignLeft) x = label_rect.left(); else if (alignment() & Qt::AlignHCenter) x = label_rect.left() + dx / 2; else if (alignment() & Qt::AlignRight) x = label_rect.right() - font_rect.width(); if (alignment() & Qt::AlignTop) y = label_rect.top() + font_rect.height(); else if (alignment() & Qt::AlignVCenter) y = label_rect.top() + dy / 2; else if (alignment() & Qt::AlignBottom) y = label_rect.bottom(); QPainterPath path; path.addText(x, y, font(), text()); painter.fillPath(path, palette().windowText()); painter.strokePath(path, QPen(QColor(255, 0, 0, 50), 2)); } But i still dont understand the difference btw native paint event and my own

@Faruq QML (using Canvas element) and QtQWidgets (using QPainter in combination with QPainterPath) is capable of drawing such things. In either way it's all about the math and doing the calculations of each shape (arcs, lines, texts, ...) The bottom image is rather easy. Yyou just need to calculate the translation along the x-axis based on your input values which make up the direction.

Don't @ the moderators unless you have an issue requiring moderation. Depending on the content of your line edit, you can use toLatin1() or toUtf8() rather than making these two conversions.

Thank you all, the issue is solved.

If you want stylesheet ready for the use of qss in your application use this site: https://qss-stock.devsecstudio.com

@goldstar2154 Totally agree with you - there is a obvious bug. But thanks to @raven-worx 's code we've got a way to get a result at least. And "solved" will help in web search:) Thank you very much for this question:)

@IMAN4K Hi Im not sure what "material ripple animation" really is so its hard to say which design i would prefer. Copying Paint of QMenu would be last choice as there might be bugs and its involving to keep in sync. If the items can do all the drawing them self i would go for that. (2 i think :)

@mr_max I also have the same issue..Is it working now?

@fortyff said in Undefined referance to class::function: There are the same errors occured in the "esimplelabel.cpp" file, but I didn't write down here, since it'll consume too much place. Make sure you have all virtual functions that are declared defined. While a declaration of a regular function without a definition is perfectly valid (until it's called), that's not true for virtual methods.

I finally managed to get custom colors. I gave my QTreeView an object name to be able to write this in CSS: m_treeView->setObjectName("MyTreeView"); m_treeView->setStyleSheet("QTreeView#MyTreeView::item {color: none;}"); basically now my model controls text color through Qt::ForegroundRole regardless of the application's CSS. I feel like it's the wrong place to put theming, but it works for me at the moment. Well... until we decide to have different themes :-°

@Lucan1d you made me curious, and so i played around a bit. This example renders the widget and forwards mouse- and key-events to the widget (i used a QTextEdit in this case). But it also points out the problems very well: you can't use widgets with popup windows (e.g. combobox) cursor blinking and text-selection isn't painted (may be fixed somehow - didn't investigate further) correct focus handling might be pretty tricky to implement correct state handling is essential for visual appearance But i think it might be a good starting point. It still needs a lot of work to behave as someone would expect it to behave. qmlRegisterType<MyQmlWidget>("com.test.qml", 1, 0, "MyQmlWidget"); QQuickView *qmlView = new QQuickView; qmlView->setSource(QUrl::fromLocalFile("test.qml")); qmlView->show(); test.qml import QtQuick 2.0 import com.test.qml 1.0 MyQmlWidget { focus: true } h class MyQmlWidget : public QQuickPaintedItem { Q_OBJECT public: MyQmlWidget( QWidget* widget = new QTextEdit ); virtual bool eventFilter(QObject *, QEvent *); virtual void paint(QPainter * painter); virtual bool event(QEvent * e); protected: void setWidget( QWidget* widget ); QWidget* m_Widget; }; cpp MyQmlWidget::MyQmlWidget( QWidget* widget ) : QQuickPaintedItem() { this->setWidget( widget ); this->setAcceptedMouseButtons(Qt::AllButtons); } bool MyQmlWidget::eventFilter(QObject * watched, QEvent * event) { if( watched == m_Widget ) { switch( event->type() ) { case QEvent::Paint: case QEvent::UpdateRequest: this->update(); break; } } return QQuickPaintedItem::eventFilter(watched, event); } void MyQmlWidget::paint(QPainter *painter) { if( !m_Widget ) return; m_Widget->render( painter ); } bool MyQmlWidget::event(QEvent *event) { switch( event->type() ) { case QEvent::MouseButtonPress: case QEvent::MouseButtonRelease: case QEvent::MouseButtonDblClick: case QEvent::KeyPress: case QEvent::KeyRelease: { qDebug() << "SEND EVENT:" << event; QApplication::sendEvent( m_Widget, event ); return true; } break; case QEvent::FocusIn: this->forceActiveFocus(); break; } return QQuickPaintedItem::event(event); } void MyQmlWidget::setWidget(QWidget *widget) { m_Widget = widget; m_Widget->installEventFilter( this ); const QSizeF sh = m_Widget->sizeHint(); this->setImplicitSize( sh.width(), sh.height() ); }

You'r welcome ! Since you have it working now, please mark the thread as solved using the "Topic Tool" button so other forum users may know a solution has been found :)

Hi Lays, when you already have a layout set, you don't need to create a new one. Just access your existing Layout with the layout() function. In general every QWidget has its own layout (there are different kinds of layouts) and you can add widgets to them. So if you want to add a widget to your QMainWindows layout you can call inside your main windows code something like this: this->layout()->addWidget(new Widget); For further information please read http://doc.qt.io/qt-4.8/layout.html. Greetings AlexRoot

Nice! Thanks for sharing :)

Oh, then it has nothing to do with a console or a console. qDebug is a text stream. To redirect output of qDebug use qInstallMessageHandler.

Ohh. Sounds great!! Thank you for adding some new things in my knowledge base. :)

@Chris-Kawa I just have to say this is hilarious and spot on. I did this same thing in wxWidgets a couple years ago and this was my experience verbatim. In the end I went on to use the same basic technique that is described here: https://github.com/deimos1877/BorderlessWindow. Thanks for making me feel less stupid.

Hi, and thank you. For improve appearance might to add it "QGroupBox {margin-bottom: 3px;}" "QGroupBox::title { subcontrol-position: bottom; " " top: 3px; }"

Well, it was caused by a QGraphicsEffect on the QWidget. After removing it, the QWebEngineView worked without any flaws. weird.

HI, I suggest to open a new post because you marked this as SOLVED. BTW if you moved to windows and want to see the debug output you should add CONFIG += console to your .pro file