Hello,
the current implementation of the Ribbon QAT, together with the sample code for a customization dialog, has IMHO two weaknesses:
1) A category "Not in the ribbon" (like in Office2010) is missing. Thus, commands (like e.g "Undo") which are NOT in a ribbon, will disappear from QAT forever when they are deselected in the dialog (given these commands are not in the "common items" list).
I would suggest to support such a category in the future.
2) Collecting ControlReferences does not work very well if you allow the same command in more than one tab. This will probably happen if you work with different contextual tabs for different objects, providing commands like e.g. "Delete from database" or "Print Preview" for each of these objects. The result is that the same command can have multiple resource references, making it almost impossible to prevent the QAT from duplicate command icons.
I would suggest to better collect "CommandReferences" instead of ControlReferences.
Regards,
D. Peters (crew of Mr. Gesell)
the current implementation of the Ribbon QAT, together with the sample code for a customization dialog, has IMHO two weaknesses:
1) A category "Not in the ribbon" (like in Office2010) is missing. Thus, commands (like e.g "Undo") which are NOT in a ribbon, will disappear from QAT forever when they are deselected in the dialog (given these commands are not in the "common items" list).
I would suggest to support such a category in the future.
2) Collecting ControlReferences does not work very well if you allow the same command in more than one tab. This will probably happen if you work with different contextual tabs for different objects, providing commands like e.g. "Delete from database" or "Print Preview" for each of these objects. The result is that the same command can have multiple resource references, making it almost impossible to prevent the QAT from duplicate command icons.
I would suggest to better collect "CommandReferences" instead of ControlReferences.
Regards,
D. Peters (crew of Mr. Gesell)
