3ddd2dff37
Unlike object or posemode (where items not only need to be active but also selected to be treated as a starting point for cycling through to the next item behind it on the next click), armature editmode would treat active (but unselected) bones as a starting point as well. Leading to confusion if you just clear your selection prior. For reference to the expected behavior, look at these comments in `mouse_select_eval_buffer` >/* Only exclude active object when it is selected. */ >/* When the active object is unselected or not in `buffer`, use the nearest. */ Now for editbones, the way `get_nearest_editbonepoint` works, there were actually two things preventing stuff from happening as expected: - [1] we would still get "use_cycle" behavior if we have an unselected (active) bone -> this is now checked for by looking at active bone selection flags (NOTE: tip/root needs to be looked at as well). These checks were once there,bd59781c66removed them though. - [2] without "use_cycle" behavior, we are still looping all hit bones and there could be the situation where we could accept a first bone (in the `bias > bias_max` condition -- that one could be the closest already but does not set the `min_depth`), but continue to loop (now entering the "bias == bias_max && do_nearest" condition and `min_depth` could still be at INT_MAX) and accept a bone that is actually further away... That logic is from328ec2b172Both points have now been addressed. Pull Request: https://projects.blender.org/blender/blender/pulls/140348
Blender
Blender is the free and open source 3D creation suite. It supports the entirety of the 3D pipeline—modeling, rigging, animation, simulation, rendering, compositing, motion tracking and video editing.
Project Pages
Development
License
Blender as a whole is licensed under the GNU General Public License, Version 3. Individual files may have a different but compatible license.
See blender.org/about/license for details.