I am reviewing a design change in a desktop application. The proposed change is implemented with standard clickable buttons in a menu bar, appearing to the right of the normal menu items. These are standard action buttons, like the ones you would use for an OK button in a dialog (although they carry out an action more akin to what menu items are normally used for). Note that this is not a tool bar; these buttons appear on an otherwise normal menu bar with pull down menus like File and Edit.
Here's a representative shot of just the menu bar:
It seems self evident to me that it would be better to put these commands in a standard pull down menu, perhaps augmented by additional commands in a contextual menu or toolbar. It is apparently not a self evident to the other programmer, though.
I am looking for clear design guidelines that directly address whether components other than pull down menus belong in a pull down menu. I found one such reference from Oracle, but Apple and Microsoft UX guidelines seem silent on the issue.
If possible, I'd like something more specific than the ubiquitous "use components for what they were designed for," although I realize this comment does address this issue.
Alternatively, if this has somehow become acceptable in some UX designs, pointing to examples or design guidelines saying so would also be appreciated.