>But you know what??? I keep forgetting that the menu is OO in MM. In the menu you can contain properties.... >So in a cbar class you can call your form like this:
>Doform('AFormToCreate', this) && "this" is the cbar object

I like that it is OO

But I'm not a fan of all the PAD, POPUP, Bar visual classes. Also why two class libs the amenus and atmenus ?? I can see that a moderately complex having 100s of visual class objects for menus, that seems like a nightmare to keep track of, especially when it seems most of the time 1-3 attributes are being set and few methods ( click for example ) have concrete code, jumping back and forth between objects IMO is a pain.

Therefore I just moved all of these visual classes into a PRG. ( I may split the PRG into one per major menu group ) I still have all of the classes but they are now in one easy ( for me at least ) to deal with place.

Anthony