Windows Rich Text Control Development

[Kp]

It may be preferable for memory-usage reasons not to store the font name within the control, but rather to save an object which holds a reference count and a font handle.  Then all the segments drawn in a single font share one FontContainer, which is freed when they're all erased.  For example:

class FontContainer {
    HANDLE hFont;
    unsigned count;
    LPWSTR wszName;
  public:
    static FontContainer *getFont(LPWSTR font_name); // return an existing FontContainer if one is available, otherwise load the named font and return it in a new container
};

With regard to selection support, it looks like your present scheme has a selection granularity of one text segment.  This could be annoying if you wanted to select part of a line, as could happen if you were selecting a URL from someone saying "This site rocks: protocol://someplace.net/".

[MyndFyre]

With regard to selection support, it looks like your present scheme has a selection granularity of one text segment.  This could be annoying if you wanted to select part of a line, as could happen if you were selecting a URL from someone saying "This site rocks: protocol://someplace.net/".

Yes, I've considered that much.  We can create two integral values that have the beginning and ending of the selection text for zero-based indices; it shouldn't be too much trouble.  What I was going for in this case was more the general idea behind the way I think the library should work, more than the general object set.

As far as font objects -- good idea!  I hadn't thought of that.

[edit]Skywing: I found an MSDN article describing the process of laying out and drawing text using Uniscribe.  Wow.  Yes, you were definitely right: it looks like a major pain in the behind.  Thanks for the heads-up.