[Ohrrpgce] SVN: jay/3270 gfx_directx backend, v1.6a; and backend interfaces, update. Added messag

[Mike Caron]

subversion at HamsterRepublic.com wrote:
> jay
> 2009-12-31 13:25:13 -0800 (Thu, 31 Dec 2009)
> 801
> gfx_directx backend, v1.6a; and backend interfaces, update. Added message system to gfx backend, though I don't know how to declare void pointers in freebasic (gfx.new.bi, gfx.new_x.bi). Also added another callback sent at backend initialization: DefGfxMessageProc(). This function will handle all messages that the backend doesn't understand. It is implemented by the engine.

As far as pointers go, 'Any' is equivalent to 'void'. So, "foo as Any 
ptr". Obviously, cannot be dereferenced without a cast of some kind:

cptr(foo, integer ptr)

> gfx_msg.h defines the different messages that may be sent. More can be added, but they include support for all backend's different functionality (including fb's bit depth, border, sdl's zoom, etc.).
> 
> "Get" style messages are allowed and defined, too.
> 
> Also added command line options functionality back into the gfx_directx--now that a messaging system is in place, these commands are parsed and sent to the new interfaces.

I still don't know that I find the idea of messages attractive. How 
close are these to Windows messages? Is there a queue? Do you need to 
maintain a message pump? Can you Send Messages, or just Post them?
> ---
> U   wip/gfx.new.bi
> U   wip/gfx.new.h
> U   wip/gfx.new_x.bi
> U   wip/gfx_directx/source/gfx_directx.cpp
> U   wip/gfx_directx/source/gfx_directx.new.cpp
> U   wip/gfx_directx/source/gfx_directx.new.h
> U   wip/gfx_directx.dll
> A   wip/gfx_msg.h
> _______________________________________________
> Ohrrpgce mailing list
> ohrrpgce at lists.motherhamster.org
> http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org

-- 
Mike