I can see wanting to encode other information in the notation data. We should be able to add a notation attribute for user data that doesn't get displayed.
Associating more information with custom notation types feels less solid though. It seems like it should be the script's job to maintain an association between custom notation types and performing particular actions. It doesn't feel right for REAPER to store user information that always has a 1:1 association with data it's already storing.
|