blender/source/gameengine/Ketsji/KXNetwork/KX_NetworkMessageSensor.cpp

284 lines
7.5 KiB
C++
Raw Normal View History

2002-10-12 11:37:38 +00:00
/**
* $Id$
*
* ***** BEGIN GPL LICENSE BLOCK *****
2002-10-12 11:37:38 +00:00
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License
* as published by the Free Software Foundation; either version 2
* of the License, or (at your option) any later version.
2002-10-12 11:37:38 +00:00
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program; if not, write to the Free Software Foundation,
* Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
*
* The Original Code is Copyright (C) 2001-2002 by NaN Holding BV.
* All rights reserved.
*
* The Original Code is: all of this file.
*
* Contributor(s): none yet.
*
* ***** END GPL LICENSE BLOCK *****
2002-10-12 11:37:38 +00:00
* Ketsji Logic Extenstion: Network Message Sensor generic implementation
*/
#include "KX_NetworkMessageSensor.h"
#include "KX_NetworkEventManager.h"
#include "NG_NetworkMessage.h"
#include "NG_NetworkScene.h"
#include "NG_NetworkObject.h"
#include "SCA_IObject.h"
#include "InputParser.h"
#include "ListValue.h"
#include "StringValue.h"
#ifdef HAVE_CONFIG_H
#include <config.h>
#endif
2002-10-12 11:37:38 +00:00
#ifdef NAN_NET_DEBUG
#include <iostream>
#endif
KX_NetworkMessageSensor::KX_NetworkMessageSensor(
class KX_NetworkEventManager* eventmgr, // our eventmanager
class NG_NetworkScene *NetworkScene, // our scene
SCA_IObject* gameobj, // the sensor controlling object
const STR_String &subject,
PyTypeObject* T
) :
SCA_ISensor(gameobj,eventmgr,T),
m_Networkeventmgr(eventmgr),
m_NetworkScene(NetworkScene),
m_subject(subject),
m_frame_message_count (0),
m_BodyList(NULL),
m_SubjectList(NULL)
2002-10-12 11:37:38 +00:00
{
BGE patch: add state engine support in the logic bricks. This patch introduces a simple state engine system with the logic bricks. This system features full backward compatibility, multiple active states, multiple state transitions, automatic disabling of sensor and actuators, full GUI support and selective display of sensors and actuators. Note: Python API is available but not documented yet. It will be added asap. State internals =============== The state system is object based. The current state mask is stored in the object as a 32 bit value; each bit set in the mask is an active state. The controllers have a state mask too but only one bit can be set: a controller belongs to a single state. The game engine will only execute controllers that belong to active states. Sensors and actuators don't have a state mask but are effectively attached to states via their links to the controllers. Sensors and actuators can be connected to more than one state. When a controller becomes inactive because of a state change, its links to sensors and actuators are temporarily broken (until the state becomes active again). If an actuator gets isolated, i.e all the links to controllers are broken, it is automatically disabled. If a sensor gets isolated, the game engine will stop calling it to save CPU. It will also reset the sensor internal state so that it can react as if the game just started when it gets reconnected to an active controller. For example, an Always sensor in no pulse mode that is connected to a single state (i.e connected to one or more controllers of a single state) will generate a pulse each time the state becomes active. This feature is not available on all sensors, see the notes below. GUI === This system system is fully configurable through the GUI: the object state mask is visible under the object bar in the controller's colum as an array of buttons just like the 3D view layer mask. Click on a state bit to only display the controllers of that state. You can select more than one state with SHIFT-click. The All button sets all the bits so that you can see all the controllers of the object. The Ini button sets the state mask back to the object default state. You can change the default state of object by first selecting the desired state mask and storing using the menu under the State button. If you define a default state mask, it will be loaded into the object state make when you load the blend file or when you run the game under the blenderplayer. However, when you run the game under Blender, the current selected state mask will be used as the startup state for the object. This allows you to test specific state during the game design. The controller display the state they belong to with a new button in the controller header. When you add a new controller, it is added by default in the lowest enabled state. You can change the controller state by clicking on the button and selecting another state. If more than one state is enabled in the object state mask, controllers are grouped by state for more readibility. The new Sta button in the sensor and actuator column header allows you to display only the sensors and actuators that are linked to visible controllers. A new state actuator is available to modify the state during the game. It defines a bit mask and the operation to apply on the current object state mask: Cpy: the bit mask is copied to the object state mask. Add: the bits that set in the bit mask will be turned on in the object state mask. Sub: the bits that set in the bit mask will be turned off in the object state mask. Inv: the bits that set in the bit mask will be inverted in the objecyy state mask. Notes ===== - Although states have no name, a simply convention consists in using the name of the first controller of the state as the state name. The GUI will support that convention by displaying as a hint the name of the first controller of the state when you move the mouse over a state bit of the object state mask or of the state actuator bit mask. - Each object has a state mask and each object can have a state engine but if several objects are part of a logical group, it is recommended to put the state engine only in the main object and to link the controllers of that object to the sensors and actuators of the different objects. - When loading an old blend file, the state mask of all objects and controllers are initialized to 1 so that all the controllers belong to this single state. This ensures backward compatibility with existing game. - When the state actuator is activated at the same time as other actuators, these actuators are guaranteed to execute before being eventually disabled due to the state change. This is useful for example to send a message or update a property at the time of changing the state. - Sensors that depend on underlying resource won't reset fully when they are isolated. By the time they are acticated again, they will behave as follow: * keyboard sensor: keys already pressed won't be detected. The keyboard sensor is only sensitive to new key press. * collision sensor: objects already colliding won't be detected. Only new collisions are detected. * near and radar sensor: same as collision sensor.
2008-06-22 14:23:57 +00:00
Init();
}
void KX_NetworkMessageSensor::Init()
{
m_IsUp = false;
2002-10-12 11:37:38 +00:00
}
KX_NetworkMessageSensor::~KX_NetworkMessageSensor()
{
}
CValue* KX_NetworkMessageSensor::GetReplica() {
// This is the standard sensor implementation of GetReplica
// There may be more network message sensor specific stuff to do here.
CValue* replica = new KX_NetworkMessageSensor(*this);
if (replica == NULL) return NULL;
// this will copy properties and so on...
CValue::AddDataToReplica(replica);
return replica;
}
// Return true only for flank (UP and DOWN)
bool KX_NetworkMessageSensor::Evaluate(CValue* event)
{
bool result = false;
bool WasUp = m_IsUp;
m_IsUp = false;
2002-10-12 11:37:38 +00:00
if (m_BodyList) {
m_BodyList->Release();
m_BodyList = NULL;
}
if (m_SubjectList) {
m_SubjectList->Release();
m_SubjectList = NULL;
}
2002-10-12 11:37:38 +00:00
STR_String toname=GetParent()->GetName();
STR_String subject = this->m_subject;
vector<NG_NetworkMessage*> messages =
m_NetworkScene->FindMessages(toname,"",subject,true);
m_frame_message_count = messages.size();
if (!messages.empty()) {
#ifdef NAN_NET_DEBUG
printf("KX_NetworkMessageSensor found one or more messages\n");
#endif
m_IsUp = true;
m_BodyList = new CListValue();
m_SubjectList = new CListValue();
2002-10-12 11:37:38 +00:00
}
vector<NG_NetworkMessage*>::iterator mesit;
for (mesit=messages.begin();mesit!=messages.end();mesit++)
{
// save the body
STR_String body = (*mesit)->GetMessageText();
// save the subject
STR_String messub = (*mesit)->GetSubject();
2002-10-12 11:37:38 +00:00
#ifdef NAN_NET_DEBUG
if (body) {
cout << "body [" << body << "]\n";
}
#endif
m_BodyList->Add(new CStringValue(body,"body"));
// Store Subject
m_SubjectList->Add(new CStringValue(messub,"subject"));
2002-10-12 11:37:38 +00:00
// free the message
(*mesit)->Release();
}
messages.clear();
result = (WasUp != m_IsUp);
// Return always true if a message was received otherwise we can loose messages
if (m_IsUp)
return true;
// Is it usefull to return also true when the first frame without a message??
// This will cause a fast on/off cycle that seems useless!
2002-10-12 11:37:38 +00:00
return result;
}
// return true for being up (no flank needed)
bool KX_NetworkMessageSensor::IsPositiveTrigger()
{
// printf("KX_NetworkMessageSensor IsPositiveTrigger\n");
//attempt to fix [ #3809 ] IPO Actuator does not work with some Sensors
//a better solution is to properly introduce separate Edge and Level triggering concept
return m_IsUp;
2002-10-12 11:37:38 +00:00
}
/* --------------------------------------------------------------------- */
/* Python interface ---------------------------------------------------- */
/* --------------------------------------------------------------------- */
/* Integration hooks --------------------------------------------------- */
PyTypeObject KX_NetworkMessageSensor::Type = {
PyObject_HEAD_INIT(&PyType_Type)
0,
"KX_NetworkMessageSensor",
sizeof(KX_NetworkMessageSensor),
0,
PyDestructor,
0,
__getattr,
__setattr,
0, //&MyPyCompare,
__repr,
0, //&cvalue_as_number,
0,
0,
0,
0
};
PyParentObject KX_NetworkMessageSensor::Parents[] = {
&KX_NetworkMessageSensor::Type,
&SCA_ISensor::Type,
&SCA_ILogicBrick::Type,
&CValue::Type,
NULL
};
PyMethodDef KX_NetworkMessageSensor::Methods[] = {
{"setSubjectFilterText", (PyCFunction)
KX_NetworkMessageSensor::sPySetSubjectFilterText, METH_O,
(PY_METHODCHAR)SetSubjectFilterText_doc},
2002-10-12 11:37:38 +00:00
{"getFrameMessageCount", (PyCFunction)
KX_NetworkMessageSensor::sPyGetFrameMessageCount, METH_NOARGS,
(PY_METHODCHAR)GetFrameMessageCount_doc},
2002-10-12 11:37:38 +00:00
{"getBodies", (PyCFunction)
KX_NetworkMessageSensor::sPyGetBodies, METH_NOARGS,
(PY_METHODCHAR)GetBodies_doc},
2002-10-12 11:37:38 +00:00
{"getSubject", (PyCFunction)
KX_NetworkMessageSensor::sPyGetSubject, METH_NOARGS,
(PY_METHODCHAR)GetSubject_doc},
{"getSubjects", (PyCFunction)
KX_NetworkMessageSensor::sPyGetSubjects, METH_NOARGS,
(PY_METHODCHAR)GetSubjects_doc},
2002-10-12 11:37:38 +00:00
{NULL,NULL} //Sentinel
};
PyObject* KX_NetworkMessageSensor::_getattr(const STR_String& attr) {
2002-10-12 11:37:38 +00:00
_getattr_up(SCA_ISensor); // implicit return!
}
// 1. Set the message subject that this sensor listens for
const char KX_NetworkMessageSensor::SetSubjectFilterText_doc[] =
2002-10-12 11:37:38 +00:00
"\tsetSubjectFilterText(value)\n"
"\tChange the message subject text that this sensor is listening to.\n";
PyObject* KX_NetworkMessageSensor::PySetSubjectFilterText( PyObject* self, PyObject* value)
2002-10-12 11:37:38 +00:00
{
char* Subject = PyString_AsString(value);
if (Subject==NULL) {
PyErr_SetString(PyExc_TypeError, "expected a string message");
return NULL;
}
m_subject = Subject;
Py_RETURN_NONE;
2002-10-12 11:37:38 +00:00
}
// 2. Get the number of messages received since the last frame
const char KX_NetworkMessageSensor::GetFrameMessageCount_doc[] =
2002-10-12 11:37:38 +00:00
"\tgetFrameMessageCount()\n"
"\tGet the number of messages received since the last frame.\n";
PyObject* KX_NetworkMessageSensor::PyGetFrameMessageCount( PyObject* )
2002-10-12 11:37:38 +00:00
{
return PyInt_FromLong(long(m_frame_message_count));
}
// 3. Get the message bodies
const char KX_NetworkMessageSensor::GetBodies_doc[] =
2002-10-12 11:37:38 +00:00
"\tgetBodies()\n"
"\tGet the list of message bodies.\n";
PyObject* KX_NetworkMessageSensor::PyGetBodies( PyObject* )
2002-10-12 11:37:38 +00:00
{
if (m_BodyList) {
return ((PyObject*) m_BodyList->AddRef());
} else {
return ((PyObject*) new CListValue());
2002-10-12 11:37:38 +00:00
}
}
// 4. Get the message subject: field of the message sensor
const char KX_NetworkMessageSensor::GetSubject_doc[] =
2002-10-12 11:37:38 +00:00
"\tgetSubject()\n"
"\tGet the subject: field of the message sensor.\n";
2002-10-12 11:37:38 +00:00
PyObject* KX_NetworkMessageSensor::PyGetSubject( PyObject* )
2002-10-12 11:37:38 +00:00
{
return PyString_FromString(m_subject ? m_subject : "");
2002-10-12 11:37:38 +00:00
}
// 5. Get the message subjects
const char KX_NetworkMessageSensor::GetSubjects_doc[] =
"\tgetSubjects()\n"
"\tGet list of message subjects.\n";
PyObject* KX_NetworkMessageSensor::PyGetSubjects( PyObject* )
{
if (m_SubjectList) {
return ((PyObject*) m_SubjectList->AddRef());
} else {
return ((PyObject*) new CListValue());
}
}