Hello All
There are situations when a XBP Part is constructed through a
pointer retreived directly from a call to Qt wrapper. This object
is neither has any XBP parent or owner nor does it carry visual
coordinates, but still we want to exploit its other elements like
signal/slots which are already implemented in HBXBP effectively.
To avoid duplicay of efforts and keep the calls straight,
I thought two ways to encapsulate this behavior:
oBtn := XbpPushButton():new():create( , , , , , , pQtObject )
^^^^^^
additional 7th param.
oBtn := XbpPushButton():new():create( pQtObject )
^^^^^^^
theOnlyAndOnlyParam
This will be flagged as an Harbour extension.
Opinions?
BTW I have been able to exploit .ui widget resources created with Qt Creator
purely on HBXBP and HBQT levels. The above design decision has to be taken
based on opening of this new horizon.
Regards
Pritpal Bedi
--
View this message in context:
http://old.nabble.com/HBXBP---Class-Framework-Change-tp26522373p26522373.html
Sent from the Harbour - Dev mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
