| Summary: | disconnect of signals not implemented in krosspython | ||
|---|---|---|---|
| Product: | [Developer tools] bindings | Reporter: | Joris Guisson <joris.guisson> |
| Component: | general | Assignee: | Sebastian Sauer <mail> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | normal | CC: | ashl1future, cullmann, mail |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
assign to me Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved. The bindings we had are no longer maintained and got removed with either KF5 or KF6, depending on the language. |
Version: (using KDE 4.4.1) OS: Linux Installed from: Ubuntu Packages The problem is this function in pythonextension.cpp: Py::Object PythonExtension::doDisconnect(const Py::Tuple&) { //TODO return PythonType<bool>::toPyObject(false); } This means that if you connect to a signal in your script you can't disconnect and if you remove the script the function connect to it still gets called when the signal is emitted, which is even worse.