Robin Dunn

This issue has been mentioned on **Discuss wxPython**. There might be relevant details there: https://discuss.wxpython.org/t/disabling-drag-and-drop-in-a-richtextctrl/35795/2

Some implementation details that may help, if you haven't already dug into the relevant C++ code: In the GDI+ GC backend the colour value is used to create a gdi+...

The `GCDC` is still going to use the default renderer backend, which on Windows is GDI+, so I wouldn't expect any difference when using the `GCDC` vs what you were...

This issue has been mentioned on **Discuss wxPython**. There might be relevant details there: https://discuss.wxpython.org/t/a-problem-with-event-objects/35766/1

I don't like that it provides downloads based on the tag, which does not include everything that the official source archive does (none of the generated code will be present.)...

This issue has been mentioned on **Discuss wxPython**. There might be relevant details there: https://discuss.wxpython.org/t/disabling-drag-and-drop-in-a-richtextctrl/35795/3

This issue has been mentioned on **Discuss wxPython**. There might be relevant details there: https://discuss.wxpython.org/t/correct-usage-of-wx-dirdialogs-getpaths-with-dd-multiple-style/35850/5

> Is an exception that could be avoided with changes in gridmovers code? Yes, it could probably benefit from checking for the capture before capturing it or releasing it.

Is it an X11-based system or Wayland? The [current code](https://github.com/wxWidgets/Phoenix/blob/master/src/window_ex.cpp) for the generic GetHandle implementation uses `GDK_WINDOW_XID` which probably evaluates to 0 for non-X11 builds of GTK/GDK. If somebody can...

You can see more details about the wxPython part of the build by adding the `--verbose` flag to the command line. That will (among other things) print out the compile...