After that, it looped through the aClassList collection. Making it pretty I quickly realized there were a couple of things missing from my add-in. I wanted the ability to control the results, to indicate for each class whether to keep the existing class or overwrite it with a new subclass. This was significant not just to avoid overwriting existing classes but also because attempting to create a class with the same name as an existing class causes a prompt to appear. Second, I wanted a way to change the prefix and suffix of a class while subclassing.
Many developers use a prefix or suffix to indicate the level of a class in their class hierarchy.
Some use a prefix or suffix to indicate the client or project the class belongs to. So some method of specifying a prefix or suffix to be removed, and a new prefix or suffix to be applied, was called for. It was at this point that Jim Booth jumped in to help. He took on the task of handling prefixes and suffixes while I worked on dealing with duplicates. Jim suggested that rather than creating two separate forms, we use a single form with a tabless pageframe.