Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Detect top/parent move event on child widget

Detect top/parent move event on child widget

Scheduled Pinned Locked Moved Unsolved General and Desktop
qwidgetqmainwindowqmoveevent
28 Posts 6 Posters 10.6k Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • mrjjM mrjj

    @Dariusz
    Hi
    Yes on the child Widgets as an alternative to subclass them all and use moveEvent directly.
    https://doc.qt.io/qt-5/qmoveevent.html#details

    Are you saying the no such event is posted to the filter when the widgets are moved ?

    update:
    very fast test

    MainWindow::MainWindow(QWidget *parent)
        : QMainWindow(parent)
        , ui(new Ui::MainWindow)
    {
        ui->setupUi(this);
        ui->frame->installEventFilter(this);
    }
    
    bool MainWindow::eventFilter(QObject *watched, QEvent *event)
    {
    
        qDebug() << event->type();
    
        return QMainWindow::eventFilter(watched, event);
    }
    
    void MainWindow::on_pushButton_released()
    {
    
        ui->frame->move(200, 200);
    }
    
    

    Place a Frame on form
    Move it with a button
    it does report Move event

    QEvent::Polish
    QEvent::Move
    QEvent::Resize
    QEvent::Show
    QEvent::ShowToParent
    QEvent::PolishRequest
    QEvent::UpdateLater
    QEvent::WindowActivate
    QEvent::Paint
    QEvent::Paint
    QEvent::Enter
    QEvent::Leave
    QEvent::WindowDeactivate
    QEvent::Paint
    QEvent::Paint
    QEvent::WindowActivate
    QEvent::Paint
    QEvent::Paint
    QEvent::Move <<<<< the actual move via the button
    QEvent::Paint
    QEvent::WindowDeactivate
    QEvent::Hide
    QEvent::Hide

    D Offline
    D Offline
    Dariusz
    wrote on last edited by
    #5

    @mrjj said in Detect top/parent move event on child widget:

    Are you saying the no such event is posted to the filter when the widgets are moved ?

    As far as I can tell ye, have a look at this main

       ma = QMainWindow()
        ma.setCentralWidget(parentWidget())
    

    parentWidget.moveEvent() never gets fired.
    I don't mind subclassing widgets. But they don't get even moveWindow when I move mainWindow. - ma

    1 Reply Last reply
    0
    • Christian EhrlicherC Offline
      Christian EhrlicherC Offline
      Christian Ehrlicher
      Lifetime Qt Champion
      wrote on last edited by
      #6

      @Dariusz said in Detect top/parent move event on child widget:

      But they don't get even moveWindow when I move mainWindow

      Why should the children get a moveWindow event when only the parent moves? The children don't move then (relative) so no event is needed.

      Qt Online Installer direct download: https://download.qt.io/official_releases/online_installers/
      Visit the Qt Academy at https://academy.qt.io/catalog

      D 1 Reply Last reply
      2
      • Christian EhrlicherC Christian Ehrlicher

        @Dariusz said in Detect top/parent move event on child widget:

        But they don't get even moveWindow when I move mainWindow

        Why should the children get a moveWindow event when only the parent moves? The children don't move then (relative) so no event is needed.

        D Offline
        D Offline
        Dariusz
        wrote on last edited by
        #7

        @Christian-Ehrlicher Hence my question... How can I properly detect if a "on screen" position of a widget has changed on one of my child widgets?
        :- )))

        1 Reply Last reply
        0
        • Christian EhrlicherC Offline
          Christian EhrlicherC Offline
          Christian Ehrlicher
          Lifetime Qt Champion
          wrote on last edited by
          #8

          You already answered this by yourself - you know when the parent moved, so the absolute position of the child must have changed too...

          Qt Online Installer direct download: https://download.qt.io/official_releases/online_installers/
          Visit the Qt Academy at https://academy.qt.io/catalog

          D 2 Replies Last reply
          1
          • mrjjM Offline
            mrjjM Offline
            mrjj
            Lifetime Qt Champion
            wrote on last edited by
            #9

            Hi
            Ahh. now i get what you ask. The reverse.
            But why would you need to know that?
            the children will move with parents automatically.

            D 1 Reply Last reply
            2
            • mrjjM mrjj

              Hi
              Ahh. now i get what you ask. The reverse.
              But why would you need to know that?
              the children will move with parents automatically.

              D Offline
              D Offline
              Dariusz
              wrote on last edited by Dariusz
              #10

              @mrjj I have created a "new" floating widget. That user can move anywhere to screenn, but at the same time widget will move in relation to specified X widget. For example it will be a button in future. Now when button moves that can be a child of Widget>dockWidget>mainWindow changing position of mainWindow, will move button to new position thus my hover widget has to move as well. Same goes if user change dockWidget position... and there can be nested hierarchy like docket>docked>docked/etc/etc... so I'm looking if there is any way at all to be notified if a widget change its screen position at any time...

              The example above shows that. where self.w is my floating widget that is meant to follow parentWidget... but when parent widget is a centralWidget of mainWindow... then the self.w no longer gets notified to change its positionw hen parentWIdget gets moved via its parent...

              1 Reply Last reply
              0
              • Christian EhrlicherC Christian Ehrlicher

                You already answered this by yourself - you know when the parent moved, so the absolute position of the child must have changed too...

                D Offline
                D Offline
                Dariusz
                wrote on last edited by
                #11

                @Christian-Ehrlicher said in Detect top/parent move event on child widget:

                You already answered this by yourself - you know when the parent moved, so the absolute position of the child must have changed too...

                I'm not sure... as far as I can tell I have to recrusively notify all widgets children+their children+their children of position/size/ change and let them all recalculate properly.... but I'm not sure if thats the best approach...

                mrjjM 1 Reply Last reply
                0
                • D Dariusz

                  @Christian-Ehrlicher said in Detect top/parent move event on child widget:

                  You already answered this by yourself - you know when the parent moved, so the absolute position of the child must have changed too...

                  I'm not sure... as far as I can tell I have to recrusively notify all widgets children+their children+their children of position/size/ change and let them all recalculate properly.... but I'm not sure if thats the best approach...

                  mrjjM Offline
                  mrjjM Offline
                  mrjj
                  Lifetime Qt Champion
                  wrote on last edited by
                  #12

                  @Dariusz said in Detect top/parent move event on child widget:

                  as far as I can tell I have to recrusively notify all widgets children+their children+their children of position/size/ change and let them all recalculate properly

                  That's what Layouts normally are for. Automatic resize when parent is resized.

                  Did you use layouts for the children ?

                  D 1 Reply Last reply
                  0
                  • mrjjM mrjj

                    @Dariusz said in Detect top/parent move event on child widget:

                    as far as I can tell I have to recrusively notify all widgets children+their children+their children of position/size/ change and let them all recalculate properly

                    That's what Layouts normally are for. Automatic resize when parent is resized.

                    Did you use layouts for the children ?

                    D Offline
                    D Offline
                    Dariusz
                    wrote on last edited by
                    #13

                    @mrjj Yes I did, so I take I could listen to layout resizeevent/etc. But what about moveEvent?

                    mrjjM 1 Reply Last reply
                    0
                    • Christian EhrlicherC Offline
                      Christian EhrlicherC Offline
                      Christian Ehrlicher
                      Lifetime Qt Champion
                      wrote on last edited by
                      #14

                      @Dariusz said in Detect top/parent move event on child widget:

                      But what about moveEvent?

                      Again: they do not move - so there is no move event!

                      Qt Online Installer direct download: https://download.qt.io/official_releases/online_installers/
                      Visit the Qt Academy at https://academy.qt.io/catalog

                      D 1 Reply Last reply
                      0
                      • Christian EhrlicherC Christian Ehrlicher

                        @Dariusz said in Detect top/parent move event on child widget:

                        But what about moveEvent?

                        Again: they do not move - so there is no move event!

                        D Offline
                        D Offline
                        Dariusz
                        wrote on last edited by
                        #15

                        @Christian-Ehrlicher So how can I detect it? Or I have to travers entire hierarchy ?

                        1 Reply Last reply
                        0
                        • Christian EhrlicherC Offline
                          Christian EhrlicherC Offline
                          Christian Ehrlicher
                          Lifetime Qt Champion
                          wrote on last edited by
                          #16

                          This was already answered.

                          Qt Online Installer direct download: https://download.qt.io/official_releases/online_installers/
                          Visit the Qt Academy at https://academy.qt.io/catalog

                          1 Reply Last reply
                          1
                          • D Dariusz

                            @mrjj Yes I did, so I take I could listen to layout resizeevent/etc. But what about moveEvent?

                            mrjjM Offline
                            mrjjM Offline
                            mrjj
                            Lifetime Qt Champion
                            wrote on last edited by mrjj
                            #17

                            @Dariusz said in Detect top/parent move event on child widget:

                            @mrjj Yes I did, so I take I could listen to layout resizeevent/etc. But what about moveEvent?

                            well, you can add a new signal to the top parent and then hook up that signal
                            to all children. then in
                            parent moveEvent emit the signal to tell the children

                            But i cannot for the life of me understand why you need that.
                            If using layouts, the child will scale with Parent and a child is
                            NOT moved when a parent is moved. it stays in same position inside the parent. So no need for it to know it at all.

                            D 1 Reply Last reply
                            1
                            • mrjjM mrjj

                              @Dariusz said in Detect top/parent move event on child widget:

                              @mrjj Yes I did, so I take I could listen to layout resizeevent/etc. But what about moveEvent?

                              well, you can add a new signal to the top parent and then hook up that signal
                              to all children. then in
                              parent moveEvent emit the signal to tell the children

                              But i cannot for the life of me understand why you need that.
                              If using layouts, the child will scale with Parent and a child is
                              NOT moved when a parent is moved. it stays in same position inside the parent. So no need for it to know it at all.

                              D Offline
                              D Offline
                              Dariusz
                              wrote on last edited by
                              #18

                              @mrjj Did you look at the example above? The childWidget is not actually in layout or anything like that... he does not even have parent. Hes being moved by parentWidget() inside moveEvent... I'm trying to affect non-related widget... MoveEvent() moves its correctly... except that it does not when the parentWidget is inside another widget... So I'm trying to get that example code above work. Without having to recursively spam hundreds of widgets... Perhaps I should not name them childWidget/parentWidget :/

                              mrjjM 1 Reply Last reply
                              0
                              • Christian EhrlicherC Christian Ehrlicher

                                You already answered this by yourself - you know when the parent moved, so the absolute position of the child must have changed too...

                                D Offline
                                D Offline
                                Dariusz
                                wrote on last edited by
                                #19

                                @Christian-Ehrlicher said in Detect top/parent move event on child widget:

                                This was already answered.

                                Are you reffering to this?

                                @Christian-Ehrlicher said in Detect top/parent move event on child widget:

                                You already answered this by yourself - you know when the parent moved, so the absolute position of the child must have changed too...

                                What signal/slot/function does get called on child to notify it of new parent position ?

                                kshegunovK 1 Reply Last reply
                                0
                                • D Dariusz

                                  @Christian-Ehrlicher said in Detect top/parent move event on child widget:

                                  This was already answered.

                                  Are you reffering to this?

                                  @Christian-Ehrlicher said in Detect top/parent move event on child widget:

                                  You already answered this by yourself - you know when the parent moved, so the absolute position of the child must have changed too...

                                  What signal/slot/function does get called on child to notify it of new parent position ?

                                  kshegunovK Offline
                                  kshegunovK Offline
                                  kshegunov
                                  Moderators
                                  wrote on last edited by
                                  #20

                                  @Dariusz said in Detect top/parent move event on child widget:

                                  What signal/slot/function does get called on child to notify it of new parent position ?

                                  None. If a widget is moved in relation to its parent's client rect (for top-level windows the "parent's client rect" is the screen), then it's going to receive a move event. Listen to that event, if you wish, by means of installing an event filter, as already mentioned.

                                  There's no signal/slot/function that gets called on the children to notify of move, because that makes no sense. The parent moves, hence the rect of the widget (the non-client rect) moves, but children's rects are still left exactly the same relative to their parent's rect, so they ain't moving, hence no move event.

                                  Read and abide by the Qt Code of Conduct

                                  1 Reply Last reply
                                  3
                                  • D Dariusz

                                    @mrjj Did you look at the example above? The childWidget is not actually in layout or anything like that... he does not even have parent. Hes being moved by parentWidget() inside moveEvent... I'm trying to affect non-related widget... MoveEvent() moves its correctly... except that it does not when the parentWidget is inside another widget... So I'm trying to get that example code above work. Without having to recursively spam hundreds of widgets... Perhaps I should not name them childWidget/parentWidget :/

                                    mrjjM Offline
                                    mrjjM Offline
                                    mrjj
                                    Lifetime Qt Champion
                                    wrote on last edited by
                                    #21

                                    @Dariusz
                                    Ahhhhhhhhhhh. We are talking floating widgets here :)
                                    That explains a lot.

                                    When you say "child" it implies it has a parent that Widget acting as a window
                                    never has. (QDialog types being an exception)

                                    So you on the right way with moveEvent and some signal.

                                    • except that it does not when the parentWidget is inside another widget.
                                      Which would make it a child. :) but in this case, it will move with the parent automatically.

                                    In any case, you should be aware of
                                    QApplication::topLevelWidgets()

                                    that will give a list with all Windows types. those are the one, you want to move manually.

                                    D 1 Reply Last reply
                                    0
                                    • mrjjM mrjj

                                      @Dariusz
                                      Ahhhhhhhhhhh. We are talking floating widgets here :)
                                      That explains a lot.

                                      When you say "child" it implies it has a parent that Widget acting as a window
                                      never has. (QDialog types being an exception)

                                      So you on the right way with moveEvent and some signal.

                                      • except that it does not when the parentWidget is inside another widget.
                                        Which would make it a child. :) but in this case, it will move with the parent automatically.

                                      In any case, you should be aware of
                                      QApplication::topLevelWidgets()

                                      that will give a list with all Windows types. those are the one, you want to move manually.

                                      D Offline
                                      D Offline
                                      Dariusz
                                      wrote on last edited by
                                      #22

                                      @mrjj Yes I have totally failed. I should have not called it parent/child as it confused every1 and no1 has read the code :- )))

                                      So I'll try to rephrase the question here...

                                      Problem A:
                                      I have 2 widgets.
                                      WidgetA is a data widget, say QGraphicsView. - this widget can be inside layout of another widget.
                                      WidgetB is a floating window, with tools.

                                      The idea is that whenever WidgetA moves, the widgetB should move with it - as well as being able to move by itself - it's all in the python example above...

                                      The problem is, that if WidgetA is inside layout, then it no longer informs widgetB of the new position because it don't get move events.

                                      Current working "approach" that I can think off is that I have to subclass all of my widgets, and reimplement their moveEvent() & inform each child widget of new position so that they can properly handle their positioning in relationship to new parent position.

                                      On another side I'm also thinking of implementing a qApp->eventFilter() - a global one, then look for moveEvent() in there and emit signals to all registered widgets from that...

                                      Given that my app is "dynamically" build, meaning that parenting/widget hierarchy can change at any time, I'm looking for "automated" approach, hard coding stuff won't work here :- )

                                      Problem B: (just emerged)
                                      How do I et WidgetB Z depth, to be always +1 over its WidgetA so that it can be always visible above WidgetA but not visible if WidgetX moves mover it... ?

                                      TIA :- )

                                      1 Reply Last reply
                                      0
                                      • mrjjM Offline
                                        mrjjM Offline
                                        mrjj
                                        Lifetime Qt Champion
                                        wrote on last edited by
                                        #23

                                        @Dariusz said in Detect top/parent move event on child widget:

                                        Oh yes. Words can be deceiving. I did read the code but since you said child widget i still
                                        didnt get why you needed any code at all :)

                                        The problem is, that if WidgetA is inside layout, then it no longer informs widgetB of the new position because it don't get move events.

                                        But why must it be WidgetA ? should dit not be the top widget (the window) ?
                                        Or the issue is that sometimes
                                        WidgetA is a window and life is good, but then same class (WidgetA ) is used in a layout and then suddenly
                                        it cant inform widgetB any more since only top parent knows it was moved ?

                                        Something like that ?

                                        D 1 Reply Last reply
                                        0
                                        • mrjjM mrjj

                                          @Dariusz said in Detect top/parent move event on child widget:

                                          Oh yes. Words can be deceiving. I did read the code but since you said child widget i still
                                          didnt get why you needed any code at all :)

                                          The problem is, that if WidgetA is inside layout, then it no longer informs widgetB of the new position because it don't get move events.

                                          But why must it be WidgetA ? should dit not be the top widget (the window) ?
                                          Or the issue is that sometimes
                                          WidgetA is a window and life is good, but then same class (WidgetA ) is used in a layout and then suddenly
                                          it cant inform widgetB any more since only top parent knows it was moved ?

                                          Something like that ?

                                          D Offline
                                          D Offline
                                          Dariusz
                                          wrote on last edited by
                                          #24

                                          I'm sorry, my bad :- ((

                                          @mrjj said in Detect top/parent move event on child widget:

                                          @Dariusz said in Detect top/parent move event on child widget:
                                          Or the issue is that sometimes
                                          WidgetA is a window and life is good, but then same class (WidgetA ) is used in a layout and then suddenly
                                          it cant inform widgetB any more since only top parent knows it was moved ?
                                          Something like that ?

                                          Yes, since its dynamically generated UI based on a user template, the WidgetA can be inside layout of another widget, or be by itself.

                                          1 Reply Last reply
                                          0

                                          • Login

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • Users
                                          • Groups
                                          • Search
                                          • Get Qt Extensions
                                          • Unsolved