Skip to content
This repository was archived by the owner on Apr 20, 2020. It is now read-only.

Slot.notifyValueChanged purpose and behavior unclear #155

Open
burgerdev opened this issue Nov 1, 2014 · 1 comment
Open

Slot.notifyValueChanged purpose and behavior unclear #155

burgerdev opened this issue Nov 1, 2014 · 1 comment

Comments

@burgerdev
Copy link
Member

I don't quite understand why only output slots should listen on that signal, but even this does not work: Slot._sig_value_changed is not emitted anywhere.
@burgerdev
Copy link
Member Author

Slot._sig_value_changed is emitted in OpArrayCache._ensureCached(), which is as far as I can tell only triggered upon requests to output slots Output and OutputHdf5.

@burgerdev burgerdev changed the title Slot.notifyValueChanged is never called Slot.notifyValueChanged purpose and behavior unclear Mar 4, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@burgerdev