On Thu, 20 Aug 2009, Alex Strickland wrote:
Hi,
>> hbwin library does not create any GUI objects directly so the Pritpal
>> question is still open.
> Let me ask differently, we have :
> FUNC WIN_AxGetControl( hWnd, bHandler )
> What form is bHandler?
> Is there some kind of default event?
> If it handles one thing, can't it handle several?
Now you are asking about implementation details and activex
functionality. Sorry but here I cannot help you. I'm not MS-Windows
programmer or even user so you will need real MS-Windows developers
help here. Mindaugas? Pritpal?
The only one thing I can help here are technical problems in
implementation so I've just look closer at axcore.c and I have
to say that for me few things are seriously broken.
I do not understand why we have WIN_AXRELEASEOBJECT(). For me
calling this function breaks autodestructors. Pritpal?
Release() method makes something strange for me. Mindaugas?
To implement such functionality it's necessary to change
the method of iSink allocation. It has to be allocated by
hb_xgrab() and then we should only allocate holder for
iSink pointer using hb_gcAlloc(). The only one reason this
code was working without GPF traps is this line:
pSink->count = 2; /* 1 for pCP->Advice() param and 1 for Harbour
collectible pointer [Mindaugas] */
which effectively blocks executing hb_xfree() due to initialization
with 2 instead of 1. BTW I do not understand above comment. For me
it should be 1 and other code fixed.
I can make modifications which fix above problems but
they have to be verified by real MS-Windows programmers.
Mindaugas?
best regards,
Przemek
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
