2009/5/14 Jérôme Laheurte <[email protected]>: > > Okay, I played around a bit. It seems that in the customtreectrl > shipped with wxPython 2.8.9.1, the check/radio controls were drawn > using embedded bitmaps; so their appearance didn't match the user's > theme but it worked. Somewhere between 2.8.9.1 and 2.8.9.2, they began > to use wx.RendererNative, which is, in theory, the best choice but > does not, in fact, work.
Darn. I hate it when the best choice isn't the best choice :-) > Were there many bugs fixed after 2.8.9.1 ? Because considering this, > we should certainly go back to this version, since the underlying > problem is the implementation of wx.RendererNative, which we can't do > much about... I did report quite some bugs to Andrea Gavana (author of all wx.lib.agw widgets), mostly about HyperTreeList, but some in CustomTreeCtrl as well. So I'd rather not go back to older versions. He is very responsive to mail about these widgets, especially when sending patches, so I'm pretty sure he'd accept a patch if we can fix or work around this. > Or, if the virtual methods of wxDelegateRendererNative are overridable > in Python (which I doubt, but I have never tried), we can override > DrawCheckBox to use an embedded bitmap in this case, getting the > correct behaviour while keeping the newer customtreectrl. I think it is also possible to set a specific renderer, so that might also be a direction to explore (http://docs.wxwidgets.org/stable/wx_wxrenderernative.html#wxrenderernativeset) Cheers, Frank
