I don't know what was the purpose of resize(0, 0) in the first place though

In case you haven't checked, quoting https://doc.qt.io/qt-6/qwidget.html#size-prop

Note: Setting the size to QSize(0, 0) will cause the widget to not appear on screen. This also applies to windows.

Just tested 3.14-rc1 on fedora w/ wayland and couldn't trigger a crash, but found some weird behavior of the autocompletion box after moving the SC window across two screens

I found that when placing the window to a position where the autocomplete box couldn't spawn (due to limited space), it simply wouldn't spawn.

BTW - since bruno is using sway - maybe this is more a problem of sway? Is the compositor having something in its logs?

edit2: Found some more bugs when closing the IDE. I think wayland is not really stable yet b/c I never had such problems when using x11.

Thanks for testing!

In case you haven't checked, quoting https://doc.qt.io/qt-6/qwidget.html#size-prop

I didn't think to check that, sorry. Thanks for the reference!

So when does this function actually triggers closing the widget? I didn't catch the difference in behavior in this PR.

Just tested 3.14-rc1 on fedora w/ wayland and couldn't trigger a crash,

Did you test with a secondary display?

Did you test with a secondary display?

Yes, but gnome and not sway.

I was on this as well, and I came to the same conclusion :D

So when does this function actually triggers closing the widget? I didn't catch the difference in behavior in this PR.

I don't think resize(0,0) is meant to make the widget disappear: it should make it shrink to the minimum size constraints of its children. Quoting the same doc page above:

The size is adjusted if it lies outside the range defined by minimumSize() and maximumSize().

(I actually tested this on a small reproducer, if the child has a positive size, the parent doesn't resize to 0).

Maybe we should replace it with adjustSize()?

A strange thing I noticed: with resize(0,0) in place, during PopUpWidget::showEvent(QShowEvent*), at the beginning of the function the widget geometry has a non-zero size, and only after calling move() the size becomes 0x0. Seems like a strange delayed update behavior, perhaps because the widget was hidden when resize was called?

(I'm testing on sway, but I don't have a second monitor, so I tested on a virtual one. I think it should be equivalent, but I'm not 100% sure.)

EDIT: @capital-G, I've tried on sway the situations you describe on gnome, and I couldn't make them happen. When there is not enough space, the autocompletion moves so that it can be displayed.

After testing the version with adjustSize() on macOS, Windows, and Linux (Fedora+Gnome+Wayland+2 monitors) me and @capital-G and @Spacechild1 decided to merge this.