Hi, One big wish is to have history suspend when moving mirrored objects that have history. For me the biggest use of history is when mirroring curves for patterns. I can then move the original Parent curve/s or their control points and history updates the mirrored copy. But if I move both the Pa…

Could not agree more, The new history behavior is very welcomed but this is a bad issue.

Hello - This should be working now - that is, if you move both parent and child of a Mirror operation, the child will be reposiotioned according the the mirror plane - History does not break but the mirror plane (or rotation center) does not move either so there is an adjustment, in most cases, to t…

Hi @pascal Well it does work but only for one level of mirroring. But I need to do two or multiple mirrors to make most patterns from a key pattern, otherwise you lose the benefit of mirroring with history. In the attached file 1.I first create the key pattern 2.Mirror the key pattern (Here hist…

Hi RM - I am not sure I follow - in uyour file the parent objects to steps 1 and 2 are in step 3. In any case, nested mirroring is respected but the mirror plane is never moved with the objects. Note in the V8 WIP, you can choose a planar object as the mirror plane; this can be moved with the object…

Hey Pascal, I don’t know how the functionality can be improved so the new history features remain intact, but IMO there is a logical fallacy currently. I get it, in V7 we cannot relocate the control which in this case is the mirror plane. A welcomed addition during a recent SR is that if the cont…

[image] Yianni: When a child object is dragged without its control, history should break. I believe this is still always the case. Do you have an example where that is not true? -Pascal

Sure, Pls select all objects and drag them. Example.3dm (997.2 KB)

Hi Yianni - if all objects are selected and moved then there is no case where a child is moved without its parent. Selecting and moving one prong will break history as expected however because all the prongs are children, and one is a parent as well. Does that make sense or am I missing the point? -…

Hi Pascal, The point here is that the control, which was an axis in a polar array is not selectable. Unless the user can translate the control, this new history behaviour is erroneous. A good example is flow along curve where the control is editable and everything follows logic.

Well, yes, it would be good to have an object as the axis as in Revolve. My guess is that is possible and even on the list, but I’ll add it if not. RH-65733 ArrayPolar: Geometry as axis -Pascal

Wish History to recognize when mirrored objects are moved together

Rhino Rhino for Windows

brian (Brian Gillespie) August 18, 2026, 10:34pm 13

RH-65733 is fixed in Rhino BETA

Topic		Replies	Views
Wish: Update Mirror plane with Move History Serengeti (Rhino BETA) windows , rhino8wish	1	652	November 17, 2021
Mirror Command Rhino	2	357	November 18, 2020
New rules for object History Serengeti (Rhino BETA) windows	2	953	January 27, 2023
History Bug with Mirror Rhino for Windows	0	328	August 25, 2021
Rhino History not recording two commands/more complex operations Rhino for Windows windows	3	382	March 14, 2023

Wish History to recognize when mirrored objects are moved together

Related topics