Thanks Craig.
As far as callbacks are concern, as we all know, the blitz programming language doesn't support it... if ever( mabie blitzmax will ). Unfortunitly, DirectX isn't like OpenGl, as you may know, as where you can't simply call the DirectX function itself via the userlib's DECLS file like you can with OpenGL function calls. You could come close as in writting a library to call the functions through COM directly, but again there is a library to be created and to go through.
With wrapping the DirectX functions to a managable usage for one to use with Blitz, there you have control inside the dll itself to work out any functions that require callbacks. Leave that kind of work for the dll to do and just have a wrapper function itself call the required work for you. Once the callback stuff is done, process the data anyway you like through extra functions. Hope that made some sense.
As far as callbacks are concern, as we all know, the blitz programming language doesn't support it... if ever( mabie blitzmax will ). Unfortunitly, DirectX isn't like OpenGl, as you may know, as where you can't simply call the DirectX function itself via the userlib's DECLS file like you can with OpenGL function calls. You could come close as in writting a library to call the functions through COM directly, but again there is a library to be created and to go through.
With wrapping the DirectX functions to a managable usage for one to use with Blitz, there you have control inside the dll itself to work out any functions that require callbacks. Leave that kind of work for the dll to do and just have a wrapper function itself call the required work for you. Once the callback stuff is done, process the data anyway you like through extra functions. Hope that made some sense.