Dietmar Schwertberger

The problem is still there with recent snapshots. I have just tested `wxPython-4.1.2a1.dev5259+d3bdb143-cp39-cp39-win_amd64` in the last days. P.S.: At least in my application, the call in `OnPress` to `wx.Window.GetCapture()` does...

Recently I found that wx has an event `EVT_GRID_COL_MOVE`. Unfortunately, there's no `ROW` version. Otherwise gridmovers coould be dropped.

OK, I think actually this is to be fixed on the wxPython end. - The check in `OnPress` should probably be `wx.Window.GetCapture() is None` - `evt.Skip()` should probably not be...

good In the next days I will submit a PR to fix the issue. Another PR has been merged into wxWidgets. The next version will have support for `EVT_GRID_COL_MOVE`. Then...

@mprosperi : PR #2144 is submitted. You may want to test the version at https://raw.githubusercontent.com/DietmarSchwertberger/Phoenix/ISSUE_1841/wx/lib/gridmovers.py The user interface is slightly better: The mouse is now captured again.

For your use case, please try `SetMinSize` instead of `SetSize`. `SetSize` does set the size, but a later call to `Layout` can change the size again. In general, different windows...

P.S.: If you had posted on discuss.wxpython.org instead of opening a ticket, you probably would have received an answer within a day or so.

SetSize does set the size. It's working. But Layout or window resizing will change it again. Think about your use case. Either use sizers or not. Don't expect one approach...

It _does_ set the size. The sizer will reset it as you asked it to manage the size. Add a .Layout call to your CallAfter to see the difference. Please:...

I think, this would solve the issue: https://github.com/wxWidgets/Phoenix/pull/2085