This is weird...it works here. Have you installed a plug-in maybe? like pie menus for instance? I have made some naming changes in the branch so some plug-ins will break.

I dont have pie menus but i have sculpt tools addon and mesh exctract. I will try process of elimination and see which one causes it..

It seems the addons was not the problem but my custom brushes.

I disabled the addons it made no difference, still got error.

I enable the addons but set blender to factory settings.I get no error like this.

This loads the default brushes bundled with blender. However my startup file contains my custom created brushes. I presume the old brush settings which dont contain the new stroke settings are causing the problems...

As I guess there wont be a workaround for this.

I will open my Startup file with this build and save it as a new startup file and see if this fixes the issue.

No change unfortunately, I will have to recreate the brushes when the branch will be merged to Blender Trunk

I was wrong again the problem is caused by my custom keymaping .Sorry about that. I need to find what is causing this, because I havent changed the "a" key.

It seems the default stroke method is also "a" key, however there is also another task assaigned to "a" key, when in curve stroke mode it selects all points of the curve . Other than this I have found no other explanation for a conflict. So its up to you if you would like to close this or investigate the reason, I will update my key config with the new settings after the merge. Cheers.

It must be due to the keymap storing all old property names then. So if they change the keymap conflicts with the new names. I'm not sure if we have an automatic conversion for that but my guess is that we do not. I must ask about how to provision for that.

It looks like this won't be easy to solve.

Generally the name changes are made because different paint systems support different sets of stroke modes (for instance, in trunk, texture painting does not support drag dot or anchored brushes)

To fix this I will possibly make a dynamic enum that will choose the set accordingly. This I will also do in trunk so these properties can be the same across paint systems.

For you this will mean that you will have to update the naming of that operator but only once. And I will have to be more careful about naming changes from now on :).

Hi,

It should be fixed now. To use the same keymap across branches just enter stroke_method as the property (and make sure you have a soc-paint and master branch made from commits later than tonight)

Thanks a lot Psy-fi :)