On Thu, 04 Apr 2013 13:56:18 +0200 Hans Mackowiak wrote:
HM> It would be possible with mapping GType objects to wxClassInfo Objects
HM> and then using the ClassInfo->CreateObject function,
HM> with that we have an empty wxWindow* of the currect wxWindow type
HM> where we could set the m_widget attribute
I understand that it would be possible, in principle, but as I tried to
explain in my previous message, I have serious doubts about whether this is
going to really work in practice. I.e. creating the widget would succeed,
but some class-specific methods might not work afterwards because some
initialization done in wxFoo::Create() wasn't performed. It looks much
safer to just wrap the widget inside a generic wx(Native)Window.
HM> > HM> i may need that for ScaleButton:
HM> >
HM> > I have trouble understanding what this one does and failed to find any
HM> > screenshots for it, could you please explain?
HM>
https://developer.gnome.org/gtk3/unstable/GtkScaleButton.html
HM> its a button like that:
HM>
https://developer.gnome.org/gtk3/unstable/volumebutton.png
This is a button?? Someone must have changed the meaning of this word
while I wasn't looking...
HM> i hope i did not annoy you with my ideas.
No, absolutely not, sorry if I gave you such impression (completely
inadvertently if I really did). I agree that it would be nice to be able
wrap arbitrary native widgets, there will always be some GTK+ widgets that
won't be supported by wx. I just think that, realistically, wrapping them
should be used to be able to use them alongside normal wx controls in the
dialogs and such, so basically we just need to be able to position/show/
enable them correctly. If we could have wxNativeWindow implementation
allowing to do this, it would be already great.
Regards,
VZ