Przemyslaw Czerpak wrote:
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 really appreciate your willingness to do this for Windows code. It is not
critical for me as I can live with what works in HWGUI, but that does not
help to move things forward.
I still think you did not understand what I said but I hope that I begin
to understand what you are asking for saying about multiple events.
Which part have I misunderstood? I simply thanked you for looking at this code
which has nothing to do with *nix.
You did not ask about activex functionality but about current activex
implementation in HWGUI where you have to declare separate codeblocks or
function references for each event.
I could not see how it worked in Harbour as opposed to HWGUI, there are no
examples and the COM code is pretty tough to understand.
It's not necessary in core Harbour code which uses only single handler
for all events. Sorry that it took such long time but it was really hard
to guess that you are asking about functionality present in one of Harbour
3-rd party library not sth general for Ole/Activex API. I'm not familiar
with this code.
I'm sorry to not be more clear. To confirm your deductions, I have code like
this:
CLASS BPTI FROM HActiveX
METHOD terminalDSPEvent(p1, p2, p3, p4) ;
INLINE ::Event("terminalDSPEvent", p1, p2, p3, p4)
METHOD infoEvent(p1, p2, p3, p4) ;
INLINE ::Event("infoEvent", p1, p2, p3, p4)
METHOD exceptionEvent(p1, p2, p3, p4) ;
INLINE ::Event("exceptionEvent", p1, p2, p3, p4)
METHOD Event()
...
//
// The event numbers are taken from the Type Library - ICoBpTiEvents
//
METHOD New(oWnd, cProgId, nTop, nLeft, nWidth, nHeight) CLASS BPTI
::EventMap(1, "terminalDSPEvent", self)
::EventMap(2, "infoEvent", self)
::EventMap(3, "exceptionEvent", self)
return Super:New(oWnd, cProgId, nTop, nLeft, nWidth, nHeight)
METHOD Event(cEvent, p2, p3, p4, p5) CLASS BPTI
...
With Harbour I guess I would simpy have:
METHOD Event(...) CLASS BPTI
In such case for your infornation: current Harbour code has probably
serious bugs but it's nothing worser then current HWGUI implementation
because we are talking about areas not addressed by HWGUI at all
(automatic destructors). You can use current Harbour actives implementation
to replace HWGUI code with one exception. Harbour does not support
parameters passed by reference and HWGUI does. It's important only if you
use parameters passed by reference in your event handlers.
I do not use parameters passed by reference.
I'll try to add
such functionality and fix autodestructor code but final tuning/extension
I will want to leave for real MS-Windows programers/users.
Thank you.
Regards
Alex
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
