Extra generic errors for Scene, Groups and Metaballs to raise errors when trying to do anything with a python objects thats had its data removed in Blender.

Added to existing scn.objects
scn.objects.active    (get/set the active object for the scene)

scn.objects.selected    - an iterator that only uses selected objects
scn.objects.context    - an iterator on objects in the user context (visible in the current 3d views layer and selected)
These are the same type as scn.objects but .add() .remove() .new() .active etc raise errors. so scn.objects.selected.add() will raise an error.

Made nested loops possible with scn.objects, metaball.elements and ob.modifiers, by initializing the iter value as NULL and creating copys of the pyobject when _getIter() is called if ->iter is not NULL.
This is how pythons xrange() works.

1 files changed, 1 insertions, 0 deletions

diff --git a/source/blender/python/api2_2x/Scene.h b/source/blender/python/api2_2x/Scene.h
index 6967a569859..bdf0977b075 100644
--- a/source/blender/python/api2_2x/Scene.h
+++ b/source/blender/python/api2_2x/Scene.h
@@ -57,6 +57,7 @@ typedef struct {
 	PyObject_VAR_HEAD /* required python macro   */
 	BPy_Scene *bpyscene; /* link to the python scene so we can know if its been removed */
 	Base *iter; /* so we can iterate over the objects */
+	int mode; /*0:all objects, 1:selected objects, 2:user context*/
 } BPy_SceneObSeq;