Oh what a tangled project I create. For an idea of just how complicated I got with this part of the program, just take a look at the whole form before it gets "compressed" to it's working size. But it is packed with awesome, yet fairly simple and easy to use due to the complexity hidden in the multiple frames which are only displayed according to which section of the program you are using. What started out as a simple means of adding text to a patch image blossomed into a feature where many of the various attributes which can define a font, and how it's rendered to the drawing surface, can be adjusted to create just the look you want in the finished product. Overall, it contains a lot behind the scenes to work with text:

• 3000+ lines of code
• 135 subroutines and functions
• 191 controls in use on the surface.

So the best way to describe how to use all these features is to go through each panel one by one, and explain all the functionality found on each.

The easiest and fastest means of generating some text is to simply select a font, type in some text, and press render. Clicking on the render surface pops the results where you can get a better look at it, then you can get into using features from some of the other panels to adjust the results to achieve the results you want.

Some of the quirks do need to be mentioned about this module. First is that the button for invoking the Text Maker is only a triggering button, once you actually send text to an Image Window, the system switches into Grab mode. Until you set the text to the image with a right click, any changes you make and send to the window will replace the prior text image. This quirk extends to if you were to select and grab some image space, while the Text Maker window is active, the selected chunk of image will be replaced with the sent text image. Because it's a selected chunk of text, when using the embedded version, all the Cut & Paste functions are still active, along with the ability to Delete the text. There seems to be am odd percularity with this concerning the UnDo stack at this time, will address it, however, switching to another button other than Hand or Select does not dismiss the Text Maker, and sent text to the window does not invoke either method. So the UnDo stack does not get the notification that the image changed.