Update 2014/09/26

For the past few weeks, I’ve been working through a pretty big design change. One of the features we’ve always wanted is the ability to allow users to set their own configuration — in essence, the “Options” menu.

I’ve primarily been working on “Display Settings” (resolution, window mode, antialias level). Previously, our Graphics classes provided routines to set these properties individually, but what is really needed is a way to set the entire group at once. This is because there are two common use cases:

  • At Startup, a configuration is populated either from file or using defaults.
  • In the “Options” menu, the user adjusts settings and then hits “Apply”.

In both cases, the settings are passed to the Engine as a group.

Test Display

I’m happy to report that the “Display Settings” can now be set as a group at both startup and during run-time (tester screenshot above). It seems like such a little thing, but I think it’s really cool to have that capability in our Engine.

I plan on doing a detailed write-up on this subject in the Engine section.