Skip to main content

Timeline for Conflicts between addons contexts?

Current License: CC BY-SA 4.0

10 events
when toggle format what by license comment
Jan 27, 2023 at 5:38 history edited Harry McKenzie CC BY-SA 4.0
deleted 31 characters in body
Mar 8, 2021 at 12:37 history edited Gaia Clary CC BY-SA 4.0
added 26 characters in body
May 28, 2016 at 11:32 history edited lemon CC BY-SA 3.0
added 119 characters in body
May 28, 2016 at 9:17 comment added batFINGER Not sure re conflicts, but would be a very very last resort I'd go to .. (defining my own context class) Have a look at the avastar code that is run when the fitted bones slider values are changed, and what are the properties of the sliders etc etc. Drivers?, update method?
May 28, 2016 at 9:12 comment added lemon I have searched for my properties names in the blender addons folders : no hit, except my addon. But can you confirm that conflicts are possible ?
May 28, 2016 at 9:06 history edited lemon CC BY-SA 3.0
added 328 characters in body
May 28, 2016 at 8:59 comment added batFINGER You can paste code directly into pasteall.org/69992/python Don't have Avastar to test against. Could see if gaia is on #blendercoders irc.freenode.net Does the Avastar addon have any of the scene properties you've defined scene.sourceArmature for example? Also suggest editing your question with the above details.
May 28, 2016 at 8:42 comment added lemon The "bad behaviour" is that using fitted bones sliders in Avastar does not work correctly (mesh is curiously shifted to the right). This does not happen if my addon is not registered (and with the same mesh).
May 28, 2016 at 8:26 comment added batFINGER Please elaborate, what is the other addon, what is the "behaviour" that is being influenced? Some code would be handy too...? By addon installed to you mean registered? Not sure jumping to defining your own context class is the way to go.
May 28, 2016 at 8:01 history asked lemon CC BY-SA 3.0