Chris,

>I started off wanting to move a few menu items to different pads. When I dug under the hood, the layout and contents of the menu classes seemed a little counter-intuitive to me. How did you organize them?

Actually, there is a method to my madness! I did used to have the menus organized as you propose, but this wasn't flexible enough for developers using our Framework.

1. We have all the base menu classes in CMenu.vcx...these are all the basic building blocks

2. We have custom menu pads and bars in CtMenus.vcx. This is a collection of different menu pads and bars you can choose from when building your menus, OR you can completely ignore them and create your own.

3. AtMenus.vcx is an application-level class library. We did it this way so you can build your own popups. If we put the popus in a Framework-level library, such as CtMenus.vcx, you would have to edit the Framework classes to build popups the way you want them!

Our naming convention is to use the pad name as the prefix in a bar name. If you plan to move a bar to a different menu pad, then I would definitely change its name. Again, this is only a convention...you can actually name your menu bars any way you like.

Regards,