mapToGlobal/mapFromGlobal isn't working properly

[wysota]

The parent of the popup widget is DzMainWindow, which is a subclass of QMainWindow, and are not doing our own layout. We use methods such as QMainWindow::setMenuWidget() so we are using the default layout that QMainWindow uses.

So it is managed by a layout which might explain why your own geometry management fails. If you wish to do your own moving/resizing, you can't use layouts at the same time.

We are trying to position the popup widget so that it's corners align with one of the corners of the reference widget (posWgt), based on the orientation of the divider bar and the quadrant that the reference widget.

Examples:
posWgt Quadrant: Bottom-Right
Dock Bar Orientation: Horizontal
Alignment: popupWgt's bottom-right corner should align with posWgt's top-right corner

posWgt Quadrant: Bottom-Right
Dock Bar Orientation: Vertical
Alignment: popupWgt's bottom-right corner should align with posWgt's top-left corner

posWgt Quadrant: Top-Left
Dock Bar Orientation: Horizontal
Alignment: popupWgt's top-left corner should align with posWgt's bottom-left corner

I suggest you forget about docks for now and implement your solution as working for any possible widget. When you have that done you can adjust the code to work for your specific case. mapToGlobal() and mapFromGlobal() both work fine so if they fail in your case then it has to be caused by your own code. Move the popup code out of your specific use-case, make it work as a standalone solution and then integrate it back to your main project.

[janderson.daz]

So it is managed by a layout which might explain why your own geometry management fails. If you wish to do your own moving/resizing, you can't use layouts at the same time.

That makes sense. However, as a quick test I changed the code that creates the popup so that it doesn't have a parent. Shouldn't that mean that it's position is no longer affected by the main window's layout? When I did this, I didn't see any change in behavior...

I suggest you forget about docks for now and implement your solution as working for any possible widget. When you have that done you can adjust the code to work for your specific case. mapToGlobal() and mapFromGlobal() both work fine so if they fail in your case then it has to be caused by your own code. Move the popup code out of your specific use-case, make it work as a standalone solution and then integrate it back to your main project.

I will look into doing this

[janderson.daz]

Problem has been "solved". It is not a layout issue as was suspected. While performing different tests I noticed a few things that led me to the "fix":

• The geometry before and after the move was different
• This caused the final x and y coordinates to be off by a certain amount
• I noticed that the amount the coordinates were off also happened to coincide directly with the geometry changing (e.g. If the x coordinate was off by 4 pixels from what was expected, the width of the final geometry would change by 4 pixels. The same was true for the y coordinates).

These things led me to believe that I was calculating my positions based on bad geometry, which would in turn cause my positions to be incorrect... I tried calling updateGeometry() on the popup widget but that didn't have any effect.

As a test, I tried calling move on the popup widget before calculating my offsets. This turned out to work! So, for some reason that I can't figure out, the geometry is not correct until after the first time the widget has been moved.

I admit this is a bit hackish but I get the results I want. Everything lines up perfectly now. I am open to other solutions if anyone has any to offer. Until then this is how we are "fixing" the problem.