QWidget top level widget
-
@Alexey-Serebryakov
Ohh.
Like Win 10 Toast messages?But you must run on other platforms and prefer your own ?
https://doc.qt.io/qt-5/qtwidgets-desktop-systray-example.html
also for full blown usage
https://github.com/mohabouje/WinToast -
@mrjj yes, like Win 10 Toast.
Application run on Windows 10 and Ubuntu. So I need show custom popup widget. :-(
Thank you but built-in systray not allowed.Ok, it must be totally custom.
QSystray also had issues on ubuntu over the years.So is the message also clickable like Toats are or is it more like a tooltip type ?
-
Ok, it must be totally custom.
QSystray also had issues on ubuntu over the years.So is the message also clickable like Toats are or is it more like a tooltip type ?
-
@mrjj Yes there popup widget has title, text, image, close button, links and so on. User can click them and follow to the main window by context dependency. Also popup widget can contain other user-defined custom widget.
Oh so its a FancyToast widget ;)
Well it should not be that hard to place it. and the rich part sounds lovely.
Do notice on some virtual Desktops, its like one big screen and you will have to move your window
to right x pos as there will be only 1 screen. -
Oh so its a FancyToast widget ;)
Well it should not be that hard to place it. and the rich part sounds lovely.
Do notice on some virtual Desktops, its like one big screen and you will have to move your window
to right x pos as there will be only 1 screen.@mrjj what the FancyToast?
-
Oh so its a FancyToast widget ;)
Well it should not be that hard to place it. and the rich part sounds lovely.
Do notice on some virtual Desktops, its like one big screen and you will have to move your window
to right x pos as there will be only 1 screen.@mrjj yeah virtual desktop is next my head ache... :-)
-
Instantiating a
QWidgetand callingshow()create a series of events that get processed asynchronously. It cannot be safely assumed thatwindowHandle()returns a valid pointer right after construction and/or callingshow(). You might be more lucky on Win10, than on UBuntu/X11.If you want to wait for the widget to be fully constructed, you have to wait for
windowHandle() != nullptr, e.g. bywhile (!w1.windowHandle()) a.processEvents();QWindow::isExposed()tells if the window has been rendered on a screen. -
Instantiating a
QWidgetand callingshow()create a series of events that get processed asynchronously. It cannot be safely assumed thatwindowHandle()returns a valid pointer right after construction and/or callingshow(). You might be more lucky on Win10, than on UBuntu/X11.If you want to wait for the widget to be fully constructed, you have to wait for
windowHandle() != nullptr, e.g. bywhile (!w1.windowHandle()) a.processEvents();QWindow::isExposed()tells if the window has been rendered on a screen.@Axel-Spoerl thank you,
consider example code above,
how can I show w1 widget on first monitor and w2 on second?
Now both widgets showing on the same primary monitor. -
@Axel-Spoerl thank you,
consider example code above,
how can I show w1 widget on first monitor and w2 on second?
Now both widgets showing on the same primary monitor.how can I show w1 widget on first monitor and w2 on second?
Suggest you take a look at the documentation and examine
QWidget::setScreen(QScreen *screen). -
@mrjj is it correct code?
class Widget : public QWidget { Q_OBJECT public: Widget(QWidget *parent = nullptr) : QWidget(parent, Qt::Window) {} ~Widget(); }; int main(int argc, char *argv[]) { QApplication a(argc, argv); Widget w1; Widget w2; w1.show(); w1.windowHandle()->setScreen(QApplication::screens()[0]); w2.show(); w2.windowHandle()->setScreen(QApplication::screens()[1]); return a.exec(); }@Alexey-Serebryakov thank you
