Adding Configuration and Logging
In the last tutorial we setup the main application core that we can use as a primitive kernel
to run our games with the help of the DirectX sample framework. In this tutorial we’ll go through
adding some important pieces to your application, even if they might be “unsexy”; reading .ini config files,
and logging.
Reading INI Configuration
An important ability for your application, is to be somewhat data driven in nature. In other words, your
application loads in certain data during runtime of your game, to make decisions. While it’s dangerous
to go “hog wild” and make your codebase completely data driven, we can certainly benefit from a small
use of it.
For faster testing and to shorten development time, a bit of a data driven approach can offload some work
onto your game designer crew and/or testers instead of forcing you to re-compile any desired changes.
A good use of data driven design is reading any location-specific language data. Suppose your game has several
dialogs of text which describe a certain scene to the player. If you hardcode this text into your game,
then it means needing to re-compile the entire thing for any minor text change. It is also more difficult
to add in support for other languages, because you would need to re-compile those additions as well.









This is default description text on Padangan Themes, of course you can change this text via you profile administration.