Hi,
I have problems with OLE and variables by reference, exemple:
---cut---
oOle = Win_OleCreateObject( "NFe_Util_PL005a.Util" )
cName = ""
cMess = ""
oOle:PegaNomeCertificado( @cName, @cMess )
? cName,cMess
---cut---
I have not implemented references in OLE because of a simple reason: I
was not able to find any sample to test my code. I see Przemek added
this missing code. Thanks!
Yes that's right, thanks. Do you think it could be moved to core?
I don't use WVG, but HWGUI. The implementation by Mindaugus and
further work by Viktor and Przemyslaw look very clean and I
would prefer to use it than the ActiveX implementation in HWGUI,
but without the support for different events I cannot.
...
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?
I guess current implementation is enough. bHandler receives event
type/number as a first parameter. I do not remember if I used copy
pasted event log for my test code:
WIN_AxInit()
hWndAx := CreateWindow("ATLAXWin", "http://sf.net";, ...
oAx := WIN_AxGetControl( hWndAx, @SomeEventLogFunc() )
I used a simple logging function:
STATIC FUNC SomeEventLogFunc(...)
LOCAL aParam := {...}
AEVAL( aParam, {|X,Y| IF(VALTYPE(X)=="O", aParam[Y] := "O:" +
X:ClassName, NIL)}) // Avoid HB_VALTOEXP() crash
? HB_VALTOEXP(aParam)
RETURN
Log was:
{105, 2, .T.}
{105, 1, .F.}
{105, -1, .F.}
{102, "Finding site: www.delfi.lt"}
{108, 100, 10000}
{102, "Connecting to site 81.16.232.110"}
{102, "Web site found. Waiting for reply..."}
{108, 100, 10000}
{102, "Start downloading from site: http://www.delfi.lt/"}
{270, .T., NIL}
...
The first number is event number, but I really do not know the meaning
of it. I have a feeling that passing event number as a parameter to
handler is traditional and acceptable in windows. Just like in windows
message handlers:
LRESULT WndProc( HWND hWnd, UINT nMsg, WPARAM wParam, LPARAM lParam )
I see additional Przemek's code that distributes events into different
event handlers. I hope it help for those who do not like to write:
IF nMsg == SOME_EVENT
...
ELSE nMsg == ANOTHER_EVENT
...
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 was somehow fixed on idea about using collectible pointer to store
ISink. This way I've got into trouble of recursive GC block references
described on:
http://lists.harbour-project.org/pipermail/harbour/2009-June/020569.html
I had to initialize counter to 2, to avoid premature ISink release. GC
mark function was required to solve the problem. Thanks, for easy
solution of the problem.
Regards,
Mindaugas
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
