- User Since
- Jul 11 2018, 9:13 PM (31 w, 4 d)
Mon, Feb 11
Thu, Feb 7
Wed, Feb 6
Tue, Jan 22
Dec 19 2018
I think youre making it a bigger issue than it is. Yes the tooltip could be improved to mention the increment fallback - but how about making a concrete suggestion what it should say?
In my original tooltip there was somethign about it, maybe it was too lengthy or because of the changes it made no sense anymore - anyways its just a tooltip/wording issue, the usage of this is straight forward.
Dec 18 2018
@Ludvik Koutny (rawalanche)
builder.blender.org already has brechts iteration of this - just give a try?
you dont need to activate incremental snap - just use vertex snap and disable affect for rotate&scale. if affect is turn off these modes will always fall back to incremental snapping.
@Campbell Barton (campbellbarton) thank you for taking this up again :)
Dec 16 2018
Dec 13 2018
@Brecht Van Lommel (brecht) ah yes you are correct - all good then.
Dec 12 2018
@Brecht Van Lommel (brecht) good to hear back from you. dont worry about changeing stuff around - I think the actual implementation is pretty simple, its the design which isnt so straight forward.
Dec 9 2018
I liked the Idea from @Brecht Van Lommel (brecht) very much, as its very simple, clean and non intrusive.
Dec 7 2018
Dec 4 2018
@Brecht Van Lommel (brecht) glad you also feel this way - I didn't dare to propose such a thing :)
Dec 3 2018
@Germano Cavalcante (mano-wii) this does not work, as other tools also use these snap flags. Now you can only control these for move/rotate/scale - but you can't control the snapping in other modes like shrink wrap anymore.
I already feared to have missed the window of opportunity, but with the release on the horizon it's also very understandable.
Dec 2 2018
Nov 30 2018
@William Reynish (billreynish) I will change the implementation to follow the propsal then. thanks for your input.
@William Reynish (billreynish) basically I want to have vertex/increment snapping at the same time, but rotate should not snap to any vertices - as in denser models there is basically a vert everywhere and it shouldnt mess with the incremental snapping. It also kinda defeats the point of incremental snapping as it introduces 'uneven' values again. Im well aware that its a bit on 'one has to explain this' side...
Nov 29 2018
makes sense to revert it for now, and the reasoning why it is the way it is is much clearer - as this was kinda vague on the intial revert comments on this topic.
Nov 28 2018
@Hjalti Hjálmarsson (hjalti) so youre basically using the gizmo version all the time with normal/local to do 'regular' transformations and the G key as a shortcut for global transformations? (now that is an interessting usage scenario..)
bold move guys :)
Nov 25 2018
Nov 24 2018
Nov 23 2018
Nov 22 2018
Nov 21 2018
ah, good to see you already tried that .. and good to see I toyed with the correct piece of code.
@Campbell Barton (campbellbarton) thank you for your time updating this patch! learned a thing or two from your changes - I know you have a lot on your plate, so this is really appreciated.
Nov 20 2018
- reverted changes to bmesh_bisect_plane.c
- changed to using BM_ITER_MESH_MUTABLE instead of the stack
Nov 19 2018
Oct 23 2018
this can be closed. I retried this every once in a while - in the version from 21.10.2018 I can now open my files again ( build: blender-2.80-13cfb641c6d-win64 ) thank you!
Jul 26 2018
hey thanks for taking the time looking into this.