By accident I discovered that Keys that have a dot in their name form a layered structure in the Model Attribute Key list. Is it by design? If so, they cut out the last sublayer and form more than one top layers.
Sorry, but Rhino’s quality is getting me into trouble again.
I was about to use and modify my scripts from a few months ago and it’s like they rot in the meantime and stopped working. Investigation showed that the problem reported in Rhino 8.6 was fixed in 8.7 but returned in 8.8…
I already started to be accustomed to changes made in newer Rhino versions, but I need to roll back and it’s not my first rollback in the Rhino 8.
Having dot in the Key name creates nested Key structure which I can’t reference. In my work I’m dealing with Keys coming from real project and I can’t change their name.
This is what I found out. In Rhino 8.7.24134.3001 Entering the Key assignment popup menu once changes the behavior of the Group Content component and makes it read Key inputs.
We are planning to release a hot fix on 8.8 for this issue.
If you have the time please install Rhino 8.8 with the hotfix from here and confirm us is fixed or not on your side.
Probably it was working differently earlier, I noticed that now there must be an expression in the Key input that modifies the Key text to search in the correct group. If one knows about it, it’s fine and working as it should.
Keys with dots in their names are still making groups (but one group, not duplicated) so I assume this is by design, and I’m ok with that.