In article <45942BB9.17447.186F10@twegner.swbell.net>, "Tim Wegner" <twegner@swbell.net> writes:
Rich asked:
How upset would people be if fractint.cfg went by the wayside?
Not too upset. Fractint.cfg really doesn't make sense except for the DOS video environment. My only concern is whether we might want to use the video abstraction to support non-GUI graphics or not.
The rest of the code isn't changing, we're just not loading the video table from fractint.cfg -- its loaded by asking each driver to add its video modes to the table. At the moment, when you switch video modes it doesn't switch drivers, which it will need to do. When I add in the logic for multiple drivers, this will happen. As you recall the driver interface routes everything through a set of function pointers for the basic operations of I/O: getting a key press, plotting a pixel, etc. To switch drivers, you switch the global pointer g_driver to point to another driver structure and all the vectors are changed for the basic I/O. So I need to add a little bit of code to the video mode select screen to switch the driver pointer if the current driver is not the one providing the video mode. -- "The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download <http://www.xmission.com/~legalize/book/download/index.html> Legalize Adulthood! <http://blogs.xmission.com/legalize/>