UPBGE: Remove SG_QList from PyObjectPlus.

Previously this class was used only for implicit list maagement for logic bricks
and armature channels/contraints.
This class already caused a lot of issue due to it's destructor, also since it's
plan to replace it by std::vector at the end, reduce it's power in the code is
the best.

For the moment logic bricks and armatures contraints/channels stil inherite from
SG_QList but not though PyObjectPlus.

Author: panzergame

source/gameengine/Converter/BL_ArmatureChannel.h

@@ -35,6 +35,8 @@
 #include "DNA_action_types.h"
 #include "EXP_PyObjectPlus.h"
 
+#include "SG_QList.h"
+
 class SCA_IObject;
 class KX_GameObject;
 class BL_ArmatureObject;
@@ -43,7 +45,7 @@ struct bPoseChannel;
 struct Object;
 struct bPose;
 
-class BL_ArmatureChannel : public PyObjectPlus
+class BL_ArmatureChannel : public SG_QList, public PyObjectPlus
 {
 	// use Py_HeaderPtr since we use generic pointer in proxy
 	Py_HeaderPtr;

source/gameengine/Converter/BL_ArmatureConstraint.h

@@ -35,6 +35,7 @@
 #include "DNA_constraint_types.h"
 #include "EXP_PyObjectPlus.h"
 
+#include "SG_QList.h"
 #include <map>
 
 class SCA_IObject;
@@ -50,7 +51,7 @@ struct bPose;
  *            head = BL_ArmatureObject::m_controlledConstraints
  * SG_QList : not used
  */
-class BL_ArmatureConstraint	: public PyObjectPlus
+class BL_ArmatureConstraint : public SG_QList, public PyObjectPlus
 {
 	Py_Header
 

source/gameengine/Expressions/EXP_PyObjectPlus.h

@@ -43,7 +43,6 @@
 #include "EXP_Python.h"
 #include "STR_String.h"
 #include "MT_Vector3.h"
-#include "SG_QList.h"
 #include <stddef.h>
 
 #ifdef WITH_PYTHON
@@ -554,19 +553,7 @@ public: \
 
 #endif
 
-
-// By making SG_QList the ultimate parent for PyObjectPlus objects, it
-// allows to put them in 2 different dynamic lists at the same time
-// The use of these links is interesting because they free of memory allocation
-// but it's very important not to mess up with them. If you decide that 
-// the SG_QList or SG_DList component is used for something for a certain class,
-// they cannot can be used for anything else at a parent level!
-// What these lists are and what they are used for must be carefully documented
-// at the level where they are used.
-// DON'T MAKE ANY USE OF THESE LIST AT THIS LEVEL, they are already used
-// at SCA_IActuator, SCA_ISensor, SCA_IController level which rules out the
-// possibility to use them at SCA_ILogicBrick, CValue and PyObjectPlus level.
-class PyObjectPlus : public SG_QList
+class PyObjectPlus
 {				// The PyObjectPlus abstract class
 	Py_Header							// Always start with Py_Header
 

source/gameengine/Expressions/intern/PyObjectPlus.cpp

@@ -63,7 +63,7 @@ PyObjectPlus::~PyObjectPlus()
 #endif
 }
 
-PyObjectPlus::PyObjectPlus() : SG_QList()				// constructor
+PyObjectPlus::PyObjectPlus() // constructor
 {
 #ifdef WITH_PYTHON
 	m_proxy= NULL;

source/gameengine/GameLogic/SCA_ILogicBrick.h

@@ -40,7 +40,7 @@ class KX_NetworkMessageScene;
 class SCA_IScene;
 class SCA_LogicManager;
 
-class SCA_ILogicBrick : public CValue
+class SCA_ILogicBrick : public SG_QList, public CValue
 {
 	Py_Header
 protected:

source/gameengine/GameLogic/SCA_IObject.h

@@ -35,6 +35,8 @@
 #define __SCA_IOBJECT_H__
 
 #include "EXP_Value.h"
+
+#include "SG_QList.h"
 #include <vector>
 
 class SCA_IObject;