Recently in Rhino 8 I’ve noticed something weird when naming/renaming a material:
Click on a layer material in the Layer tab
When the material edit window pops up, edit the name of the material to something new
Now when you hit the Enter key it closes that window as excepted, but it also cancels the rename
On the other hand:
Click on a layer material in the Layer tab
When the material edit window pops up, edit the name of the material to something new
Click on any of the controls (reflectivity, roughness, etc.) on that edit page (you don’t even need to move a slider, just click on it)
Now when you hit the Enter key it closes that window as excepted and the rename actually sticks this time
I’m not exactly sure when Rhino 8 started doing this, but I feel like it’s probably since the last update (I’m on SR5).
maxsoder
(Max Söderström)
April 5, 2024, 10:16am
3
Logged the bug and fixed it in 8.7.
RH-81415 Modal Content editor name change bug
2 Likes
I’ve installed Rhino 8 SR7 2024-5-17, but I am still seeing the same behavior with this name change bug.
maxsoder
(Max Söderström)
May 22, 2024, 10:02am
5
I will reopen the bug.
The new attempt to fix this is now in v8.9.
Edwin8
(Edwin)
June 18, 2024, 2:53am
6
Hi Max Just bumping, Agreed still the same behaviour which is also affecting Enscape-based materials as well. Additionally:
Running 8.7.24138.15431, 2024-05-17
When Enscape materials are duplicated in the Rhino material manager, they don’t show up in the Enscape material editor.
When Materials are duplicated they can’t be renamed and even the default duplicated name doesn’t update and refresh in Enscape Materials.
Hope it Helps
Many thanks,
Edwin
maxsoder
(Max Söderström)
June 18, 2024, 7:39am
7
@Edwin8 Thanks, I made a YT for this problem RH-82603 Duplicated material does not show up in Enscape material editor
maxsoder
(Max Söderström)
July 26, 2024, 7:47am
8
@Edwin8 We looked at RH-82603 Duplicated material does not show up in Enscape material editor with Enscape developers and we could not reproduce. It might be that we do something differently? Is this still a problem? We might need more specific steps how to test this.
Regards, Max