Hi Pritpal,
>> 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.
Question is: why?
> 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
Why should this conversion be done on the object wrapper level?
Why can't you do this conversion in QT_QPIXMAP()?
F.e. in hb_gcpointer()?
Brgds,
Viktor
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
