I think that the ! _MatchProperties command should keep the object History after reading the custom mesh settings from another object.

Hi @Rhino_Bulgaria I just ran into this myself a couple of days ago. I didn’t even post about it but I’m glad you did. Surely this can be fixed? RM

[image] 3dsynergy: Surely this can be fixed? Yes, this seems like an oversight, the object ID is not changed after MatchProp, but the history record seems to get trashed. Most of the other MatchProp settings do retain the history, so I guess this is a bug. Looks like it exists in the WIP as…

In my opinion, History must not affect object properties other than when the actual geometry is being modified via surfacing or editing tools.

[image] Bobi: In my opinion, History must not affect object properties other than when the actual geometry is being modified via surfacing or editing tools. In the few quick tests I made here, I only see History being broken when matching custom mesh settings. Matching other properties does …

I tested all options inside the “Match properties” panel and I can confirm that only matching the custom mesh settings destroys the history. In another recent thread some people were asking for the command to not affect the History. I also agree with that one.

Hi @Helvetosaur Thanks for making the report. RM

Bug: "Match Properties" destroys the object History

Rhino Rhino for Windows

brian (Brian Gillespie) May 24, 2023, 4:39am 7

RH-74866 is fixed in the latest WIP

Topic		Replies	Views
Wish: Add "Apply last used Match object properties" command Rhino for Windows windows	1	299	June 11, 2025
Object properties not updating according to history on Rhino 7 Rhino windows	1	153	February 9, 2024
Match Properties in Rhino fro mac Rhino for Mac	10	2694	March 25, 2015
"match curve" breaks history Rhino for Windows	11	543	June 13, 2019
Match is a bit buggy Rhino for Windows	9	1440	June 6, 2014

Bug: "Match Properties" destroys the object History

Related topics