wx.NewIdRef test
Eric Fahlgren <[email protected]> Mon, 25 Jun 2018 11:26:17 -0700
| Newsgroups | gmane.comp.python.wxpython.devel |
|---|---|
| Message-ID | <CAP2Qz+VZweP=QdHLpWHLpA5yDoD0eRyi=dRAPuaFamC0R2O0wQ@mail.gmail.com> |
I just installed wxPython-4.0.3a1.dev3856+a55c2fc6-cp27-cp27m-win_amd64.whl on Win 10 64, Python 2.7.14 x64, changed all my "static id" calls to wx.NewIdRef, ran our full regression suite and did a couple dozen interactive tests instrumented to show me the ids generated. I made sure to re-use the generated ids at least a half dozen times in wx.MenuItem creation/destroy cycles. (Also in the mix are are probably hundreds of ID_ANY/wx.Window.NewControlId uses, so it has been getting exercised since the day after you released 4.02.) Everything worked just fine. Thanks again, Robin, I'm confident this is a good patch. -- You received this message because you are subscribed to the Google Groups "wxPython-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.