Python method Set Pivot to unmasked has no effect #73859

New Issue

Matthias Pieroth · 2020-02-16T00:35:42+01:00

Matthias Pieroth commented

2020-02-16 00:35:42 +01:00

System Information
Operating system: Win 10
Graphics card: NVidia GTX 1060

Blender Version
2.83 Master

Short description of error
I call this line of Python code in the invoke method of an operator in sculpt mode, the move tool is selected:

bpy.ops.sculpt.set_pivot_position(mode='UNMASKED')

But the gizmo doesnt move to the unmasked area of the mesh. When I do the same operation using the UI (Toolbar: Set Pivot) it works.

I debugged the Blender code and the function

static int sculpt_set_pivot_position_invoke(bContext *C, wmOperator *op, const wmEvent *event)

isn't executed for the Python call.

Operators like the mask_flood_fill can be called for they have exec-API callback - does set_pivot_position need an exec-callback as well so that it can be called by Python?

**System Information** Operating system: Win 10 Graphics card: NVidia GTX 1060 **Blender Version** 2.83 Master **Short description of error** I call this line of Python code in the invoke method of an operator in sculpt mode, the move tool is selected: bpy.ops.sculpt.set_pivot_position(mode='UNMASKED') But the gizmo doesnt move to the unmasked area of the mesh. When I do the same operation using the UI (Toolbar: Set Pivot) it works. I debugged the Blender code and the function static int sculpt_set_pivot_position_invoke(bContext *C, wmOperator *op, const wmEvent *event) isn't executed for the Python call. Operators like the *mask_flood_fill* can be called for they have exec-API callback - does *set_pivot_position* need an exec-callback as well so that it can be called by Python?

Matthias Pieroth commented

2020-02-16 00:35:42 +01:00

Added subscriber: @Jayanam

Pablo Dobarro was assigned by Matthias Pieroth

2020-02-16 17:25:31 +01:00

Germano Cavalcante commented

2020-02-17 14:07:21 +01:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2020-02-17 14:07:21 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Germano Cavalcante commented

2020-02-17 14:07:21 +01:00

We require steps to reproduce the problem.
This facilitates the investigation process.

We require steps to reproduce the problem. This facilitates the investigation process.

Matthias Pieroth commented

2020-02-17 19:53:08 +01:00

@mano-wii

Go to sculpt mode, remesh a cube to increase the resolution
Add a simple mask with the mask brush, invert the mask
Select the move tool/brush
open a Python console and type in

bpy.ops.sculpt.set_pivot_position(mode='UNMASKED')

to invoke the set_pivot_position operator

Nothing happens, it is not invoked.

@mano-wii 1. Go to sculpt mode, remesh a cube to increase the resolution 2. Add a simple mask with the mask brush, invert the mask 3. Select the move tool/brush 4. open a Python console and type in ``` bpy.ops.sculpt.set_pivot_position(mode='UNMASKED') ``` to invoke the set_pivot_position operator ![image.png](https://archive.blender.org/developer/F8345569/image.png) Nothing happens, it is not invoked.

Germano Cavalcante commented

2020-02-17 19:55:50 +01:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Jacques Lucke commented

2020-02-18 13:11:15 +01:00

Added subscriber: @JacquesLucke

Jacques Lucke commented

2020-02-18 13:11:15 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Jacques Lucke commented

2020-02-18 13:11:15 +01:00

It seems to work when you do this: bpy.ops.sculpt.set_pivot_position('INVOKE_DEFAULT', mode='UNMASKED'). Does this solve your issue?

It seems to work when you do this: `bpy.ops.sculpt.set_pivot_position('INVOKE_DEFAULT', mode='UNMASKED')`. Does this solve your issue?

Germano Cavalcante commented

2020-02-18 13:33:21 +01:00

Changed status from 'Needs User Info' to: 'Archived'

Germano Cavalcante closed this issue

2020-02-18 13:33:21 +01:00

Germano Cavalcante commented

2020-02-18 13:33:21 +01:00

The problem is that this operator does not have an exec callback.
You can work around the problem by specifying the context 'INVOKE_DEFAULT'.
https://docs.blender.org/api/current/bpy.ops.html#execution-context

Thanks for the report, but this is not considered a bug. Closing as this bug tracker is only for bugs and errors.

For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

The problem is that this operator does not have an exec callback. You can work around the problem by specifying the context `'INVOKE_DEFAULT'`. https://docs.blender.org/api/current/bpy.ops.html#execution-context Thanks for the report, but this is not considered a bug. Closing as this bug tracker is only for bugs and errors. For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

Brecht Van Lommel commented

2020-02-18 13:37:51 +01:00

Added subscriber: @brecht

Brecht Van Lommel commented

2020-02-18 13:37:51 +01:00

Changed status from 'Archived' to: 'Confirmed'

Brecht Van Lommel reopened this issue

2020-02-18 13:37:51 +01:00

Brecht Van Lommel commented

2020-02-18 13:37:51 +01:00

I consider this a bug, there's no way a user of the Python API can know this without looking at the source code.

It should call invoke instead of exec automatically in this case.

I consider this a bug, there's no way a user of the Python API can know this without looking at the source code. It should call invoke instead of exec automatically in this case.

Brecht Van Lommel commented

2020-02-18 13:39:14 +01:00

This operator could also get an exec callback, there's only very few types of operators that need only invoke and no exec.

This operator could also get an `exec` callback, there's only very few types of operators that need only `invoke` and no `exec`.

Matthias Pieroth commented

2020-02-18 13:40:37 +01:00

@JacquesLucke Basically yes, but then we have two possibilities: The API documentation has to be changed, or the first parameter has to be used internally - I guess the second solution is better cause other Python method calls don't need this parameter either.

Or even better, as I mentioned in the issue, the operator should get an exec-API callback.

@JacquesLucke Basically yes, but then we have two possibilities: The API documentation has to be changed, or the first parameter has to be used internally - I guess the second solution is better cause other Python method calls don't need this parameter either. Or even better, as I mentioned in the issue, the operator should get an exec-API callback.

Pablo Dobarro was unassigned by Jacques Lucke

2020-02-18 13:54:21 +01:00

Jacques Lucke self-assigned this 2020-02-18 13:54:21 +01:00

Jacques Lucke commented

2020-02-18 13:54:21 +01:00

Added subscriber: @PabloDobarro