[KevinH]

It is not that easy. All other actions registered for keyshortcuts have fixed, translatable strings representing their functions known at compile time. There is a one to one mapping of action and function.

For clips, we do not know what name/function they will have only an action number (by clip number) at compile time. So using our current mechanism we assign shortcuts to actions/functions which are clip numbers.

Nothing else is available at compile time.

This is why and how we handle keyboard shortcuts for the first 10 plugins in the same way.

This is not something I am interested in changing. BeckyEbook's approach seems to make the most sense to me.