And two identical ‘Control points on’ entries.
Followed by two ‘Convert curve to arcs’ entries which have different commands and icons.
Three ‘Delete faces’ with their different icons.
Three ‘Elevator down’ macros with different icons and/or commands (two have Python in the command field, one has no command at all).
And a pair of identical ‘Export options’.
If the icon images are different colors then the macros are considered as different - one macro cannot have multiple images. That means the commands which work on multiple object types may have multiple macros, one with each color associated with the object type (surface, mesh, subd…) because they might be in several places, appearing in different toolbar groups.
Multiple macros with the same image and different commands may also be possible, IIRC for example a number of the mesh repair commands had the same icon in previous Rhino versions.
Yes, that’s certainly the case with some of the examples here. But it’s poor data management practice to use the same name in rows with different content. Not a big issue in this context but worth fixing.
Well, given that they have now adopted specific color schemes for the various object types, what would you propose to eliminate these ‘duplicate’ commands having different colored images for each object type?
I’d add a suffix to the name to make it unique. Could be an anonymous digit like QuadRemesh 1 and QuadRemesh 2, could be a meaningful letter like QuadRemesh M and QuadRemesh S. Whatever floats McNeel’s boat.
FTAOD, this is only changing the name of the macro (which is a combo of command and icon) not changing the command itself, the button or menu text or the tooltip.
I don’t have a problem with that, I have done similar for my custom workspace where I even have different macro names for LMB/RMB commands on the same button.
Note that Rhino is not calling these macros by name - otherwise having duplicate names wouldn’t work at all - internally they are probably referenced by something like a unique GUID.
Indeed, and changing the names, as one can, would cause havoc!
