Hello Viktor
Viktor Szakáts wrote:
>
>> TODO: Method SomeQtClass:new( ... )
>> ::pPtr := QSomeClass( ... )
>> In above construct it is not known how many parameters
>> are of type pointer and otherwise and how, if resolved,
>> be forwarded to Qt wrapper with (...) syntax.
>
> Again maybe I'm missing something, but in this
> case isn't the pointer unwrapping done by inside
> QSomeClass() ? I mean if you pass parameters
> as is, why would you need to make any transformations
> on them, when this transformation can be done
> at destination function.
>
> IOW it's shouldn't be caller's responsibility
> to resolve any such internal details, and current
> patch seemed to have addressed just that, so
> maybe it's already okay.
>
It should been like this, but unfortunately it is not.
The conversion is done on the PRG level and it is effective.
But for some classes, the constructor accepts variable
number of parameters and hence (...) syntax is used.
So if I know how to put back on stack the changed parameters
retieved in :new() method, then this issue is done.
I am looking for something like:
Method QPixmap:new(...)
LOCAL aP := hb_aParams()
aeval( aP, {|x| x := hbqt_ptr( x ) } )
Qt_QPixmap(...) /* How this can be achieved with above syntax */
RETURN Self
Regards
Pritpal Bedi
--
View this message in context:
http://old.nabble.com/SF.net-SVN%3A-harbour-project%3A-13275--trunk-harbour-tp26826400p26831039.html
Sent from the Harbour - Dev mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
