Weird issue with callback functions

[Brian Alvarez]

 Hello Charles, i am experiencing an issue with a callback function. I am trying to get an example to
work:

http://www.jose.it-berater.org/smfforum/index.php?topic=5438.msg23730#msg23730

But, even though everything seems fine, it doesnt work as expected.

This line of code:

Code: [Select]

origlvproc = SETWINDOWLONG(hlistview, GWL_WNDPROC, @NEWLVPROC)   
Is supposed to subclass a listview, when NEWLVPROC is a callback function declared as follows:

Code: [Select]

FUNCTION NEWLVPROC(SYS hwnd, DWORD msg, SYS wparam, SYS lparam) AS INT
NEWLVPROC never gets fired, in fact there is absolutely no action on that function.

 However, when the function is a callback, as follows:

Code: [Select]

FUNCTION NEWLVPROC(sys cbhndl, uint cbMsg, sys wParam, sys lParam) as int callback
 The messages come trough just fine.

 Normally that would fix the issue. However, there are tons of code that uses regular functions as callback functions, and i would like to be able to port those as well. Do you know what is going on in the background? As far as i know a uint = dword, so, i have no idea what is happening. In fact, compiling the exact same code in PowerBASIC causes the exact oposite, fails with callback and works with regular functions. And other oposite stuff as well.

 Thanks for any help.
 

[Brian Alvarez]

I believe being able to use non-conventional callback functions is important, because there is a number of system API's that require having callback functions with different parameter configurations. Even one of the sorting features requires this.

[Charles Pegge]

Hi Brian,

In o2, callback functions preserve the ebx, esi and edi registers, whereas normal internal functions do not.

To make any set of functions fit for callbacks, you can put them into an extern block, so that external callers won't get these registers messed up.

extern
...
end extern

[Brian Alvarez]

Thanks Charles, i will see how can i implement this to be done automatically...

[Brian Alvarez]

Ok, from now on, when a function is used with CODEPTR, the function will be generated between extern/end extern tags.