In D7124#170706, @Bartosz Moniewski (monio) wrote:

@Simon Thommes (simonthommes) Can you elaborate on your use case for this nose? For me it works fine and this rotation flipping behavior is actually ok.
My use case:

With setup above I have local space location but world space rotation and scale. By plugging/unplugging first three outputs I can decide what works in local space and what is world space.

I've tested the patch

Patch works as intended for me.
Usecase:
-intuitive and easy way of inverting an euler rotation with the same rotation vector (rotating back and forth)
-replicating the 'Texture' rotation type from the mapping node
-much less cluttered rotation type dropdown menu by dropping

@Charlie Jolly (charlie) Sounds good to me. I would say match point, as it is standard in mapping.
But it might also be nice to match the additional euler options to all the types from the mapping node... eventually...

Okay, thanks for looking into it!
I think, the way it is right now it is more confusing than it is useful. But that is my personal preference.
I would have expected a different interaction with the naming given.