[wx-dev] Re: [wx 2.8.7, WinXP, mingw] Custom Control Positioning Problems

Vadim Zeitlin vadim at wxwidgets.org
Mon Mar 3 07:29:05 PST 2008


On Mon, 03 Mar 2008 09:50:56 +0100 Wouter van Teijlingen <wote at dare.nl> wrote:

WvT> VZ> FWIW I think we could support client data in wxRadioBox in wx itself. 
WvT> VZ> This would involve moving the client data methods from wxItemContainer 
WvT> VZ> down to wxItemContainerImmutable but this shouldn't be a problem. And 
WvT> VZ> doing the changes in wx should be simpler than duplicating all the item 
WvT> VZ> positioning code.
WvT> 
WvT> I think that's the way to go, but we don't have the resources to implement 
WvT> this functionality for other platforms. This seems as a requirement for 
WvT> acceptance in wxWidgets.

 This is not quite true. We definitely prefer having the implementation for
all 3 major platforms (GTK, Mac, MSW) but it's acceptable to have the
functionality for just one or two of them if it doesn't have any negative
effects on the remaining platforms. I.e. in this case the code must still
compile and work not worse than before on the other platforms too.

WvT> Thus for now a custom control seems the way to go. The thing is that 
WvT> positioning still fails mysteriously. Perhaps someone could take a look at 
WvT> that?

 Sorry, I really have no idea why would this happen.

WvT> wxVector indeed seems a smart choice. Currently i'm writing this custom 
WvT> control for wxWidgets 2.8.7, but i can't find wxVector in the documentation.

 It's similar to std::vector (it's a subset of it in fact).

 Regards,
VZ





More information about the wx-dev mailing list