[wx-dev] XTI

[Stefan Csomor]

Hi

>
> > WX_BEGIN_HANDLERS_TABLE(MyXTIFrame)
> > 	WX_HANDLER( ButtonClickHandler , wxCommandEvent )
> > WX_END_HANDLERS_TABLE()
> 
> Is this a comletely new event system or does it sit on top
> of the current system? I see no ID in the lines above so
> I don't understand how the event should find its way from
> the wxButton to the MyXTIFrame::ButtonClickHandler method
> (if that is what you meant).

it is using the existing event system, the line above only indicates
that MyXTIFrame has a method
called ButtonClickHandler that is taking a wxCommandEvent as parameter,
making this a 'event sink' for any 'event source' that emits a
wxCommandEvent, in the designer eg the button got connected to such a
sink, the xml streamed out this connection, and upon reading in it was
made again using 'Connect'

> > > 3) I'd say that wxxVariant (as you wrote in a comment)
> > >    should be merged with wxVariant. Stefan, did you remember
> > >    why you did not use wxVariant right from the beginning?
> >
> > it is using a templated approach, so while it could be merged
> > with wxVariant technically, I don't see how it could be
> > implemented with it
> 
> It looks like a copy of wxVariant (even the name) and I agree
> with Francesco that it should be merged with it. Is there
> anything that wxxVariant can do that wxVariant cannot do
> or cannot be made to do?
> Maybe we can extend wxVariant with a templated version (maybe
> wxVariantT <t> or something) and which doesn't need macros.

it was once meant to be the successor, therefore I tried to stay along
wxVariant, but it needs templates to function properly (or at least it
needed it once), broken compilers made the once rather clear template
implementation use more and more macros, so one important question will
be whether VC6 has to be supported, and which gcc minimum version we
want, this would allow to remove some hacks, and lead to cleaner user's
code.

Best,

Stefan