Operator panel changes revert to last saved settings, which don't include some values essential for operation.... #78814

New Issue

Nathan Vasil · 2020-07-11T01:53:20+02:00

Nathan Vasil commented

2020-07-11 01:53:20 +02:00

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00

Blender Version
Broken: version: 2.83.2, branch: master, commit date: 2020-07-09 05:50, hash: 239fbf7d93
Couldn't test on 2.90 alpha, crashed almost immediately on trying to create the simple test file, hash 39b525e0l07f or 39b525e0107f, I can't tell from the About screen or copy/paste.

Short description of error
As far as I can tell, changes to an operation (via the operator box) work by undoing the operation, then redoing it with the new settings. In order to undo the operation, Blender reverts to a saved state. However, some setting changes in Blender do not prompt a state save. Some of those state changes are essential to the actual operation being completed. That means that some operations cannot be edited without reverting some essential parameters to those operations, which screws up the whole operation. (That sounds confusing. If you follow along with reproducibility below, it will make more sense.)

Some places where Blender doesn't save a change state, that are essential to operations, include selection of active vertex group and weight paint brush settings.

Although I don't believe cursor placement prompts a state save, that doesn't seem to be a problem-- testing by placing a cursor, doing an object transform, then editing in the operator panel, didn't cause the same problems that I've seen. (I suspect that some operations save some values, like cursor location, as hidden parameters, rather than recalculating from the last saved state.)

Exact steps for others to reproduce the error
Here's a file:

operatorbug.blend

Enter weight paint mode on the cube. Change the active vertex group to "Group". From search, use "smooth vertex weights" operation. Open an operator panel and change the iterations to 2. The active vertex group changes to Group.001, changing the operation of the smooth vertex weights operation, and which group is active cannot be changed from the operator panel.

As mentioned, there are other places where this is an issue (although maybe it's worth mentioning that I always seem to run into it while weight painting.)

The workaround seems to be to trigger a state save after doing these save-less operations like change of active vertex group, by toggling in and out of edit mode.

My preferred solution to this problem would be to have state saved after many of these operations, as it also affects undo (and I use undo a lot when weight painting, it's always kind of irritating to have to redo my falloff curves after an undo.) But I'm sure that I don't know all of the costs to that.

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00 **Blender Version** Broken: version: 2.83.2, branch: master, commit date: 2020-07-09 05:50, hash: `239fbf7d93` Couldn't test on 2.90 alpha, crashed almost immediately on trying to create the simple test file, hash 39b525e0l07f or 39b525e0107f, I can't tell from the About screen or copy/paste. **Short description of error** As far as I can tell, changes to an operation (via the operator box) work by undoing the operation, then redoing it with the new settings. In order to undo the operation, Blender reverts to a saved state. However, some setting changes in Blender do not prompt a state save. Some of those state changes are essential to the actual operation being completed. That means that some operations cannot be edited without reverting some essential parameters to those operations, which screws up the whole operation. (That sounds confusing. If you follow along with reproducibility below, it will make more sense.) Some places where Blender doesn't save a change state, that are essential to operations, include selection of active vertex group and weight paint brush settings. Although I don't believe cursor placement prompts a state save, that doesn't seem to be a problem-- testing by placing a cursor, doing an object transform, then editing in the operator panel, didn't cause the same problems that I've seen. (I suspect that some operations save some values, like cursor location, as hidden parameters, rather than recalculating from the last saved state.) **Exact steps for others to reproduce the error** Here's a file: [operatorbug.blend](https://archive.blender.org/developer/F8685043/operatorbug.blend) Enter weight paint mode on the cube. Change the active vertex group to "Group". From search, use "smooth vertex weights" operation. Open an operator panel and change the iterations to 2. The active vertex group changes to Group.001, changing the operation of the smooth vertex weights operation, and which group is active cannot be changed from the operator panel. As mentioned, there are other places where this is an issue (although maybe it's worth mentioning that I always seem to run into it while weight painting.) The workaround seems to be to trigger a state save after doing these save-less operations like change of active vertex group, by toggling in and out of edit mode. My preferred solution to this problem would be to have state saved after many of these operations, as it also affects undo (and I use undo a lot when weight painting, it's always kind of irritating to have to redo my falloff curves after an undo.) But I'm sure that I don't know all of the costs to that.

Nathan Vasil commented

2020-07-11 01:53:20 +02:00

Added subscriber: @vasiln