Automatic Font Handling Class

A while back ago, I realized that I didn't want to fill in the LOGFONT structure anymore, so I created the CAutoFont class, derived from CFont, so it can be used in place of any CFont objects that you may already have in your code. The benifit of the class is that you don't have to fill in a LOGFONT structure, or write out a huge CreateFont command. Simply define a variable of type CAutoFont, with the name of the font you want as its single parameter (Times New Roman, for example), then set its parameters as necessary:

CAutoFont font("Comic Sans MS");
font.SetBold(TRUE);
font.SetEscapement(900);
font.SetHeight(24);
CAutoFont does all of the LOGFONT and CreateFont work in the background, freeing the developer from them. Besides font manipulation functions, CAutoFont also has a function for converting its internal LOGFONT structure into a single string, which is useful if you want to store the font to the registry, for example, and a function to convert the string back. In my opinion, very useful.

I've included a sample project file with the class. Hope it serves somebody as well as it's served me.

Downloads

Download source - 3 Kb
Download demo - 24 Kb


Comments

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • On-demand Event Event Date: December 18, 2014 The Internet of Things (IoT) incorporates physical devices into business processes using predictive analytics. While it relies heavily on existing Internet technologies, it differs by including physical devices, specialized protocols, physical analytics, and a unique partner network. To capture the real business value of IoT, the industry must move beyond customized projects to general patterns and platforms. Check out this webcast and join industry experts as …

  • Today's agile organizations pose operations teams with a tremendous challenge: to deploy new releases to production immediately after development and testing is completed. To ensure that applications are deployed successfully, an automatic and transparent process is required. We refer to this process as Zero Touch Deployment™. This white paper reviews two approaches to Zero Touch Deployment--a script-based solution and a release automation platform. The article discusses how each can solve the key …

Most Popular Programming Stories

More for Developers

RSS Feeds