Original Post
Hi, I'm trying to work out a way to enable theoetical user of a module I'm writing to initialize all I need in an easy way. In other words, my functions draw things. To do that, they need some drawing function, like SetPixel, PutPixel, Plot or whatever. And that *whatever* is the problem. I'd like to use a function pointer so that a user just points which function in his library draws a pixel. So, this is what I do: void (*DrawPixel) (...); void wInitialize(HDC __hdc, int width, int height, void (*PutPixelFunction) (...)) { // some code DrawPixel = PutPixelFunction; } so that later, in my functions, I just use DrawPixel(some_hdc, x, y, color); and the user, before calling any of my drawing functions needs to initialize basic things, for example (in VS): wInitialize(hdc, 800, 600, (void (*)(...)) SetPixel); SetPixel is: COLORREF SetPixel (HDC, int, int, COLORREF); It compiles, but crashes where I'm calling DrawPixel(somehdc, x, y, color), saying that I'm "calling a function declared with one calling convention with a function pointer declared with a different calling convention". I'm not entirely sure if whole the approach is correct, but I don't know any other way to do this. Perhaps some work-around with templates? I just want to keep using the module as easy as possible with other libs than just the one in VS. I've searched and read some about function pointers and they seem good if not ideal for this purpose, so what am I doing wrong this time? ;-)
