I do strongly believe "Shift" being Extrude and duplicate, is far more useful to more users that the "Axis Plane Swap", as there mouse can easily push the gizmo plane.
Sure! This is why…
Ctrl for snapping is not hardcoded, but is already occupied in transform modal map. Gizmo interactions are hardcoded, so its reasonable to use modifier keys, unoccupied in transform modal map.
If previous functionality (locking plane) was hardcoded it seems to be safe to provide the proposed substitution in hardcoded form, since the list of a functionality to satisfy is pretty much…
Nice to see an implementation. Is linked data duplicating (alt+D by default) is supposed to be supported as well?
Laptop specific keymap will disallow to transfer keymaps between devices, so you will have to configure them from scrach each time.
Using Alt+RMB as an optional alternative instead of Alt+LMB…
Well, any generative approach will be useful, but only for generative workflows.
Indeed, alt+LMB has lots of collisions, and alt+RMB has much less of them (mostly stencils controls), could be a viable solution.
Originally all the other software has cloned AutoCAD solution for viewport orbiting via alt, which was designed to fit 2d drafting (the original purpose of AutoCAD where it is commonly used till…
As far as I remember, the main challenge was not to design menus themselves, but make them feel natural - like correspond to the way operators actually works.
For example, same correspondance…
I think it is the most worthful behaviour. For example, the same way holding ctrl temporarily enables snaping if it is disabled and vice versa - which is very useful in practice.
Aw, that explains a lot. Thank you for clarification!
Indeed, 3d cursor is a system which is supposed to be used with direct user input only, since its location has to be totally predictable.
@LukasWieg I mean that Oskey is quite challenging to reassingn in OS. Also some laptops has only one Oskey near right ctrl, and doesnot have left one.
For example in object mode RR already works like that - first R starts viewport restricted rotation and second R disables restriction. Quite common behaviour, feels pretty nice.
It would be nice to have double G press (GG) assigned to temporal restriction eliminating
So this PR is trying to make this more obvious. The vert/edge/face selection modes and menus are not important for the operations themselves.
You can try to do the transpose for sure,…
Each system has an imprint of how it was originally created, so I have an assumtion which looked convincing.
In the most mesh modeling software mesh engine has been created from operators…
At the system design level what this PR does is transposing domain-function menu matrix in function-domain form.
Function-domain form assumes that there are no domain-specific functions and…
Because these can't easily be categorized into a strict domain type.
That depicts that these operations do not have a domain type, effectively separating them from those that do.
Technically
There are many examples where you have to look in the wrong menu by the mindset you mentioned:
- Rip selected Edge Loop = Vertex -> Rip Vertices Yes, because it rips…