HMG.3.4.0 Ejemplos DLL no funcionan
Posted: Sun Apr 26, 2015 1:16 pm
Hi Pete,
I do not wish to extend in this discussion about my words/your words... because I could offend indirectly to some to people who is not present here and also is not my intention. So this question about when I said "unfair", we can let apart of this discussion.
As you said (in other words) technical proposes should be most considered.
So, revising Harbour codes, seeing CalDll32 plus functions be working in HMG 3.3.1 and now in HMG 3.4.0 (both in UNICODE) I can suppose that something wrongly was changed.
The big question is Harbour's CallDll32 + functions are working ONLY in ANSI in except when is for Windows Mobile (WinCE) and this is not good for us, because we (HMG I mean) always are keep compatibilitiy and mostly we detect automactically when is UNICODE and ANSI.
So in this way, I believing we should keep our original library (of course re-adapted to new functions in Harbour, I guess the problem is we use GetProcAddress function) and still keeping our CallDll32 in our library. Because if Harbour does not offer this differentiation: it will become a problem for us. In that way, we can say our library (who it was created by HMG) is same important than Harbour or better say: there is not problem each GUI libraries having it own function even thinking it could be duplicated. It may seem duplicated but the real history is be handled in different ways. Do you agree with this ?
So if HMG remove our original CallDll32+functions and let Harbour do the job, what to do whith this ? Most probably when Harbour will be ready to work in UNICODE regarding CallDll32 we will have to fix our app codes again...
I do not wish to extend in this discussion about my words/your words... because I could offend indirectly to some to people who is not present here and also is not my intention. So this question about when I said "unfair", we can let apart of this discussion.
As you said (in other words) technical proposes should be most considered.
So, revising Harbour codes, seeing CalDll32 plus functions be working in HMG 3.3.1 and now in HMG 3.4.0 (both in UNICODE) I can suppose that something wrongly was changed.
The big question is Harbour's CallDll32 + functions are working ONLY in ANSI in except when is for Windows Mobile (WinCE) and this is not good for us, because we (HMG I mean) always are keep compatibilitiy and mostly we detect automactically when is UNICODE and ANSI.
So in this way, I believing we should keep our original library (of course re-adapted to new functions in Harbour, I guess the problem is we use GetProcAddress function) and still keeping our CallDll32 in our library. Because if Harbour does not offer this differentiation: it will become a problem for us. In that way, we can say our library (who it was created by HMG) is same important than Harbour or better say: there is not problem each GUI libraries having it own function even thinking it could be duplicated. It may seem duplicated but the real history is be handled in different ways. Do you agree with this ?
So if HMG remove our original CallDll32+functions and let Harbour do the job, what to do whith this ? Most probably when Harbour will be ready to work in UNICODE regarding CallDll32 we will have to fix our app codes again...