|
|
Btw. this is probably better explained in the docs:
http://doc.trolltech.com/4.3/porting4-designer.html#uic-output
http://doc.trolltech.com/4.3/porting4.html
> -----Ursprüngliche Nachricht-----
> Von: Peter Prade [mailto:prade@xxxxxxxxxxx]
> Gesendet: Dienstag, 8. April 2008 19:02
> An: qt-interest@xxxxxxxxxxxxx
> Betreff: AW: Porting to/Developing in QT4
>
> some remarks:
> - qt3to4 doesn't do everything for you. in fact, it's just
> producing a starting point in your porting venture.
> - qt4 has a different scheme for uic created objects -
> they're no longer widgets themselves, instead they are used
> to populate a widget, and to keep pointers to the subcontrols created.
> - you can "simulate" the old qt3 way by multiinheriting from
> the uic generated object AND the widget of your choice.
> - a better way (the qt4 way) is to have the uic generated
> object as a member object in your widget.
>
> Cheers,
> Peter
--
To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx with
"unsubscribe" in the subject or the body.
List archive and information: http://lists.trolltech.com/qt-interest/
|
|