8 events
when toggle format what by license comment
Apr 13 '17 at 12:57 history edited CommunityBot
replaced http://blender.stackexchange.com/ with https://blender.stackexchange.com/
Aug 14 '15 at 0:42 history tweeted twitter.com/#!/StackBlender/status/631989173772267520
Aug 13 '15 at 17:45 comment added Mutant Bob This ties into my "bpy.ops has cooties" philosophy. In an ideal world each function in bpy.ops would clearly document the context it requires, but it would be a major effort to update all the docs. Even requiring that documentation for new operators would encounter resistance from the coders who are working full-tilt to keep the bugs under control while adding important new features.
Aug 13 '15 at 16:17 comment added zeffii It really comes down to people trying to use operators that aren't intended to be used anywhere other than as a response to a user clicking a menu item. During that menu interaction the operator has the correct context, but outside of it.. in a script for instance..which tends to have a sort of 'no-mans-land' (or very often the wrong ) context.. it will fail. Looking for a way to override the context, for every possible operator, is not necessary, as the context limitation is often mitigated by using more low level bpy calls. (In the end also this results in more manageable code.. )
Aug 13 '15 at 16:04 answer zeffii timeline score: 4
Aug 13 '15 at 15:55 comment added TLousky Thanks. Unfortunately I do indeed want to set the background material to use nodes via a script... I hope someone will have another idea that doesn't involved delving into the source, but if there's no choice, it won't stop me :)
Aug 13 '15 at 15:51 comment added zeffii Yeah the source is the definitive answer: I think you allude to this question ( blender.stackexchange.com/questions/30364/… ) . But you probably don't want this in the first place. Is your real problem ' i want to create a material and set it to use shader nodes - via script ' ?
Aug 13 '15 at 15:26 history asked TLousky CC BY-SA 3.0