Page MenuHome

Renaming of Vertex Groups not possible in complex projects
Closed, DuplicatePublicBUG

Description

Blender Version
Broken: blender 2.80rc1
Worked: 2.79b

Short description of error
Renaming of Vertex Groups not possible in complex projects

Exact steps for others to reproduce the error

  1. Open
  2. Double click to try to rename the Vertex Group

or

  1. Start New File
  2. add a vertex group (renaming is still possible)
  3. add an emitter (in this case: hair)
  4. increase the number: If the number is set to 100000
  5. renaming of the vertex group is not possible

Event Timeline

Can confirm on latest build. On lessen performant machines are specially remarkable (tested on centrino, 4gb RAM, intel iGPU). I tried "triple click" :D and it worked!. Seems related to some sort of buffer issue when blender is busy (this is purely speculative and can be erroneous). Thanks!

Sebastian Parborg (zeddb) lowered the priority of this task from 90 to 50.
Sebastian Parborg (zeddb) updated the task description. (Show Details)

I can confirm that I have to spam click to get it to rename. Without the heavy hair system, as simple double click will do.

@William Reynish (billreynish) feel free to reassign if this doesn't fall into the UI category.

The problem is that there is some depsgraph update here. That evaluates the modifiers and therefore the hair as well.
It loops over all particles.

Feels like the issue is that the depsgraph is evaluated when one starts editing the name of the vertex group.

This is a task for a developer to fix, not a UI design issue I think.

Changing the vertex group name should update the dependency graph, because bones and vertex groups are linked by name. I think the problem is that the first click is for changing the active vertex group, which can affect the viewport in weight paint mode for example.

There are a few things that could be improved here:

  1. If a vertex group is already active, then clicking it again should not cause any depsgraph update. (probably simple)
  2. Ideally changing the active vertex group would have more fine-grained tagging so it doesn't affect anything when it doesn't affect any viewport. (may be simple if it's a matter of checking if the object is in weight paint mode in the RNA update function, would need to be checked)
  3. Events coming from GHOST should ideally have a timestamp, and that timestamp should be used to determine the double clicking time. (too much work to handle as a bug report)

Changing the vertex group name should update the dependency graph, because bones and vertex groups are linked by name.

Am I correct that that the operation of renaming has two parts:

  1. Getting the cursor with a double click
  2. Actually changing the name after ENTER or something is pressed

If I understand correctly, (2) is the only thing that needs a non-UI update.

The issue is that on double click two different things are done:

  • On the first click, it makes the item active which require a dependency graph update.
  • On the second click, it starts renaming.

It's not the renaming that's the problem, but the making active that happens right before that.

Germano Cavalcante (mano-wii) changed the subtype of this task from "Report" to "Bug".

I can confirm in blender 2.83
In the attached file, if you add a second vertex group and try to switch the selection, you may notice a delay that may be related.