Hi, Please make it that Flip doesn’t effect history it’s for rendering and display and is a real pain to work around or to get right when working with surfaces from edge curve command. Flipping an object should not break history. Please fix for V7. RM

I agree. I also think that flipping is a necessary step just to continue building a model with history, where some rhino tools are pretty stubborn (or rather careless) about which direction to create normals. For example: _Patch would create a surface with the normals in the inverted direction of al…

Hi RM - It can indeed be a pain - but flipping constitutes ‘editing the output’ - it is not a neutral operation like changing color or something, and that is, for now, how it is. Flipping might indeed be a reasonable thing to expect History to pay attention to as Input to a history operation. Thi…

Hi @pascal I don’t really understand what you mean it seems Rhino doesn’t care which way objects are flipped Rhino is render both sides friendly. Can’t the developer just quote out that line that calls history violation seems easy as a " mark in front of line of code which wouldn’t effect any code …

[image] 3dsynergy: Can’t the developer just quote out that line that calls history violation seems easy as a " mark in front of line of code which wouldn’t effect any code or it’s functioning in other places. I don’t think it is as easy as that, I think it means a reverse history call needs t…

Hi @Gijs Even if it’s not that easy why can’t this be fixed it makes no sense? This is another faux pas in the way McNeel crafted history and refuses to listen and fix any bugs or limitations. It could be such a powerful workflow but the tons of caveats and worse the lack of McNeels interest in mak…

[image] 3dsynergy: Rhino is render both sides friendly. If rendering were the only thing that depends on surface direction, it might be that easy. Surface direction is affects a lot of stuff, but the main point here is that flipping is editing the child in a history chain - as you know, that …

What about a feature called “Update history” or “Ignore History change”, which will enable the user to preserve the History on a specific object (surface or curve) even after flipping the surface or curve direction?

A robust history implementation should automatically do what’s called “geometric matching” behind the scenes. Just as with blends and other things jumping to different edges after a trim and ruining the model, that’s completely unnecessary! History should not just record an ID, but also some charact…

Hi Pascal, But in this case flip doesn’t affect anything except breaking history. I don’t get why you can’t see the pain of it not working properly and instead defend a bad system? We’re all willing to chime in and give our thoughts and we actually already have but McNeel won’t even take the time …

Flip shouldn't affect history

Rhino Rhino for Windows

eobet (eobet) April 27, 2023, 1:35pm 7

Preach!

[Feature Request] Add “Flip Normal” Toggle in Surface Creation Dialogs

Topic		Replies	Views
[Feature Request] Add “Flip Normal” Toggle in Surface Creation Dialogs Rhino windows	7	160	May 24, 2026
Flip command break History command? Rhino for Windows	6	580	May 12, 2018
History for modeling/surfacing in Rhino needs a lot of work Serengeti (Rhino BETA) windows	9	959	June 10, 2026
Moving curve point flips resulting surface history Rhino for Windows windows	5	236	June 7, 2024
Trimming surfaces makes history crazy Serengeti (Rhino BETA)	14	1479	October 14, 2020

Flip shouldn't affect history

Related topics