Page MenuHome

clean weight selects previous VG
Closed, InvalidPublic

Description

System Information
OS: windows 7 64bit
GPU: nvidia quadro k4000

Blender Version
Broken: 2.74 official
Worked: dont know

Short description of error
when using the weight clean option and then select a different vertex group and clean again it switches back to the previous vertex group

Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps

  1. open blend file

  1. select the vertex group 1

  1. clean the vertex group

  1. select the vertex group 2

  1. change the limit to update the clean and notice how it switches back to the vertex group 1

i think the problem is that the options for the first vertex group remain visible when changing to a new vertex group and when the user changes the value it jumps back to the vertex group which the operation belongs to.
so when selecting a new vertex group the options should not show unless the user uses the clean button again.

Details

Type
Bug

Event Timeline

dan grauer (kromar) raised the priority of this task from to Needs Triage by Developer.
dan grauer (kromar) updated the task description. (Show Details)
dan grauer (kromar) set Type to Bug.

I'm pretty sure this behaviour is expected. I mean it's not really good, but that's an issue with the design of our undo system. The settings in the redo panel are for the last executed operator and selecting vertex groups isn't done using an operator.

@Bastien Montagne (mont29)/@Campbell Barton (campbellbarton) any ideas here?

Julian Eisel (Severin) lowered the priority of this task from Needs Triage by Developer to Normal.Apr 16 2015, 10:05 PM
Bastien Montagne (mont29) claimed this task.

Definitively not a bug indeed. Operator settings in panel are some kind of “advanced automatic undo/redo”, so quite obviously when you change them you first undo to state right before operator was first triggered. That’s common behavior all across Blender.

Note making that kind of selection trigger an undo step would be kind of overkill. We could add some kind of 'fake' undo step that prevent operator redo to show in panels and such, but that’s TODO/design stuff, no bug. Thanks for the report anyway.