bpy.ops.action.new() does nothing when invoked from script #51011

New Issue

Henrik Berglund · 2017-03-20T17:52:36+01:00

Henrik Berglund commented

2017-03-20 17:52:36 +01:00

System Information
Win 8.1, GTX1070

Blender Version
Broken: 2.78c e92f235283

Short description of error
bpy.ops.action.new() does nothing when invoked from a script. Maybe you're not supposed to but then why is it listed in the API?

Exact steps for others to reproduce the error
Create some object. Create an action in the action editor. Open a text editor and write

import bpy
bpy.context.area.type = 'DOPESHEET_EDITOR'
bpy.context.space_data.mode = 'ACTION'
bpy.ops.action.new()
bpy.context.area.type = 'TEXT_EDITOR'

and click run script. Nothing happens. I would expect the same thing happening that happens when you click the add action button in the UI: a new action is created with identical keyframes and then selected in the action editor list automatically.

edit: changed from Addons to BF Blender tag.

**System Information** Win 8.1, GTX1070 **Blender Version** Broken: 2.78c e92f235283 **Short description of error** bpy.ops.action.new() does nothing when invoked from a script. Maybe you're not supposed to but then why is it listed in the API? **Exact steps for others to reproduce the error** Create some object. Create an action in the action editor. Open a text editor and write ``` import bpy bpy.context.area.type = 'DOPESHEET_EDITOR' bpy.context.space_data.mode = 'ACTION' bpy.ops.action.new() bpy.context.area.type = 'TEXT_EDITOR' ``` and click run script. Nothing happens. I would expect the same thing happening that happens when you click the add action button in the UI: a new action is created with identical keyframes and then selected in the action editor list automatically. edit: changed from Addons to BF Blender tag.

Henrik Berglund commented

2017-03-20 17:52:36 +01:00

Changed status to: 'Open'

Henrik Berglund commented

2017-03-20 17:52:36 +01:00

Added subscriber: @cyaoeu

Brendon Murphy commented

2017-04-07 01:20:01 +02:00

Added subscriber: @BrendonMurphy

Brendon Murphy commented

2017-04-07 01:20:01 +02:00

Changed status from 'Open' to: 'Archived'

Brendon Murphy closed this issue

2017-04-07 01:20:01 +02:00

Brendon Murphy self-assigned this 2017-04-07 01:20:01 +02:00

Brendon Murphy commented

2017-04-07 01:20:01 +02:00

hi,
to test:
On default cube, insert keyfame 0, move timeline to 100, scale & move the cube, insert keyframe.
run this:

import bpy
bpy.context.area.type = 'DOPESHEET_EDITOR'
bpy.context.space_data.mode = 'ACTION'

A new action is created as expected.

Closing as invalid.

hi, to test: On default cube, insert keyfame 0, move timeline to 100, scale & move the cube, insert keyframe. run this: ``` import bpy bpy.context.area.type = 'DOPESHEET_EDITOR' bpy.context.space_data.mode = 'ACTION' ``` A new action is created as expected. Closing as invalid.

Henrik Berglund commented

2017-04-07 02:22:45 +02:00

What? You created the action when inserting the keyframes...

But I guess I can be more clear about what's wrong.

Default cube, insert keyframe on 0, move to 100, insert another keyframe.
Open the action editor and confirm that an action called CubeAction was created when inserting the keyframes.
Click the + sign in the action editor to create a new action. A new action called CubeAction.001 is created.
Now in the text editor, paste the code I wrote at the top and run it. No new action is created. This is a bug, what I expect is that a new action called CubeAction.002 is created, just like when pressing the + button in the action editor.

What? You created the action when inserting the keyframes... But I guess I can be more clear about what's wrong. 1. Default cube, insert keyframe on 0, move to 100, insert another keyframe. 2. Open the action editor and confirm that an action called CubeAction was created when inserting the keyframes. 3. Click the + sign in the action editor to create a new action. A new action called CubeAction.001 is created. 4. Now in the text editor, paste the code I wrote at the top and run it. No new action is created. This is a bug, what I expect is that a new action called CubeAction.002 is created, just like when pressing the + button in the action editor.

Brendon Murphy commented

2017-04-07 02:44:12 +02:00

hi, ok, getting it now.
I think probably this is a more a python support issue, I see now that indeed you are correct & your code does fail.
have you looked at blender stackexchange for similar questions?
it would seem to be that to do this by py you need to set a keyframe first?
also unsure if contexts for this operator are correct or need to be set.

hi, ok, getting it now. I think probably this is a more a python support issue, I see now that indeed you are correct & your code does fail. have you looked at blender stackexchange for similar questions? it would seem to be that to do this by py you need to set a keyframe first? also unsure if contexts for this operator are correct or need to be set.

Henrik Berglund commented

2017-04-07 03:00:38 +02:00

I saw in the Blenderartist forums that someone had the same problem, the advice that was given was to "not use the operator", which seems like a bad workaround if you really want the same behavior. I really like the + button operator, it creates a new action with the same name+.001, selects it in the action editor automatically and even copies all of the keyframes from the previous animation. Basically great for when you're making for example looping variations. The only problem with it is that it doesn't work in scripts right now.

I think the context for the operator should be correct, if you remove the bpy.context.area.type = 'DOPESHEET_EDITOR'
bpy.context.space_data.mode = 'ACTION' stuff you get a polling error. But if you execute those commands you don't get an error. To me this means that it should be correct. Nothing happens though which is a bit strange. If you're not supposed to be able to use the operator in scripts I would expect an error explaining why it can't be used. But if it's really a bug that it doesn't do anything right now I would be happy if it could be fixed.

I saw in the Blenderartist forums that someone had the same problem, the advice that was given was to "not use the operator", which seems like a bad workaround if you really want the same behavior. I really like the + button operator, it creates a new action with the same name+.001, selects it in the action editor automatically and even copies all of the keyframes from the previous animation. Basically great for when you're making for example looping variations. The only problem with it is that it doesn't work in scripts right now. I think the context for the operator should be correct, if you remove the bpy.context.area.type = 'DOPESHEET_EDITOR' bpy.context.space_data.mode = 'ACTION' stuff you get a polling error. But if you execute those commands you don't get an error. To me this means that it should be correct. Nothing happens though which is a bit strange. If you're not supposed to be able to use the operator in scripts I would expect an error explaining why it can't be used. But if it's really a bug that it doesn't do anything right now I would be happy if it could be fixed.

Brendon Murphy commented

2017-04-07 08:26:08 +02:00

Changed status from 'Archived' to: 'Open'

Brendon Murphy reopened this issue

2017-04-07 08:26:08 +02:00

Brendon Murphy commented

2017-04-07 08:26:08 +02:00

reopening for more investigation

Brendon Murphy was unassigned by Dalai Felinto

2019-12-23 16:36:45 +01:00

Germano Cavalcante commented

2020-01-23 14:34:59 +01:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2020-01-23 14:34:59 +01:00

Analyzing the bpy.ops.action.new's code, I could see that it only works when it is called from a button.
This is because it reads the button context and gets the current action through it.
This is a bad assumption, as this operator is totally useless if called in python.

Analyzing the `bpy.ops.action.new`'s code, I could see that it only works when it is called from a button. This is because it reads the button context and gets the current action through it. This is a bad assumption, as this operator is totally useless if called in python.

blender-admin commented

2020-01-23 14:43:51 +01:00

This issue was referenced by 24ebed4d84

This issue was referenced by 24ebed4d841ea9828a869d917a5718c829f09430

Germano Cavalcante commented

2020-01-23 14:45:09 +01:00

Changed status from 'Confirmed' to: 'Resolved'

Germano Cavalcante closed this issue

2020-01-23 14:45:09 +01:00

Germano Cavalcante self-assigned this 2020-01-23 14:45:09 +01:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

bpy.ops.action.new() does nothing when invoked from script #51011