← Back to team overview

linuxdcpp-team team mailing list archive

[Bug 830841] [NEW] python signalDisconnected().connect(func) type error

 

Public bug reported:

Get a type error on trying to connect with signalDisconnected()

typemap/PyHandle in python.i should be completed with something like:

(near line 212):
	void operator()(adchpp::Entity& c, adchpp::Util::Reason reason, const std::string& str);

(near line 351)
	void PyHandle::operator()(adchpp::Entity& c, adchpp::Util::Reason reason, const std::string& str) {
		PyGIL gil;
		PyHandle args(PyTuple_New(3), true);

		PyTuple_SetItem(args, 0, SWIG_NewPointerObj(SWIG_as_voidptr(&c), SWIGTYPE_p_adchpp__Entity, 0 |  0 ));
		PyTuple_SetItem(args, 1, PyInt_FromLong(reason));
		PyTuple_SetItem(args, 2, PyString_FromString(str.c_str()));

		PyHandle ret(PyObject_Call(obj, args, 0), true);
	}

** Affects: adchpp
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to ADCH++.
https://bugs.launchpad.net/bugs/830841

Title:
  python signalDisconnected().connect(func) type error

Status in ADCH++:
  New

Bug description:
  Get a type error on trying to connect with signalDisconnected()

  typemap/PyHandle in python.i should be completed with something like:

  (near line 212):
  	void operator()(adchpp::Entity& c, adchpp::Util::Reason reason, const std::string& str);

  (near line 351)
  	void PyHandle::operator()(adchpp::Entity& c, adchpp::Util::Reason reason, const std::string& str) {
  		PyGIL gil;
  		PyHandle args(PyTuple_New(3), true);

  		PyTuple_SetItem(args, 0, SWIG_NewPointerObj(SWIG_as_voidptr(&c), SWIGTYPE_p_adchpp__Entity, 0 |  0 ));
  		PyTuple_SetItem(args, 1, PyInt_FromLong(reason));
  		PyTuple_SetItem(args, 2, PyString_FromString(str.c_str()));

  		PyHandle ret(PyObject_Call(obj, args, 0), true);
  	}

To manage notifications about this bug go to:
https://bugs.launchpad.net/adchpp/+bug/830841/+subscriptions


Follow ups

References