Slot.setValue() should call self.disconnect()

Question

Slot.setValue() should call self.disconnect()

Closed this issue 12 years ago · 1 comments

It seems like a bug that it doesn't do so right now. Add a unit test for this when it is fixed.

Answer 1 · 2013-02-06T19:24:47.000Z

This isn't so important now that it is illegal to call setValue() on a slot that has an upstream partner. The code in setValue() itself already does the important stuff that calling disconnect() would do (e.g. firing the sig_disconnect() signal, calling self._changed). It could use some refactoring, but it's not worth keeping this issue open.