Problem with listeners and modifiers/custom lists

4.01K viewsCSS Bugs
0

There seems to be a bug when setting listeners to values of modifiers.

This works as expected
self.song().tracks[0].devices[0].add_chains_listener

But when using modifiers (that definately store the correct value) this doesn’t work and the listener never fires:
self.song().tracks[self.get_modifier_value("m1")].devices[self.get_modifier_value("m2")].add_chains_listener

Can someone confirm?

Hellem Answered question
Attached Files:
2

The listener is only ever refreshed when the mode is loaded. So it is essentially ‘hardcoded’ with the value of the modifier on mode load.

When you change the modifier, if you reload the active mode after it, that will update the listener to the new value.
This can be done in a reaction action: script > set active mode… (and add the mode number).

I tested this and it works.

Hellem Posted new comment
Attached Files:

It would be great to refresh specified listener with a code, not only by mode activation.

0

is there a way to add a listener to a list of parameters with one reaction?

Hellem Answered question
0

Ok, this should be documented somewhere as it is not self-explanatory. Thanks for the solution!

admin Changed status to publish
Attached Files:
0

Hey,

Sorry, we’re investigating this issue, I’ll get back to you as soon as I have info.

John

admin Changed status to publish
0

@JohnC:
This bugreport is nearly 2 weeks old now. Can you at least confirm it?
It will take you 5 minutes to recreate this scenario.
Not being able to use modifiers in listener defintions is really a big problem for me.

admin Changed status to publish