Your comments

I just started with Iridium and found out the hard way about the strange handeling of feedbacks. I got completely different results than what I expected after adding multiple feedbacks to one button.


Then I started reading the manual and it said: "The feedback channel can be assigned only once. Otherwise the incoming data will be processed incorrectly."

Why does Studio accept assigning multiple feedbacks, when the manual says it can only be assigned once ?

Why is the behavior of these multiple feedbacks not clearly described in the manual ?

I think Wouter has a good point : there should be some logic

I also understand that Aleksandr wants to keep backwards compatibility.

So, I propose the following, that can do both:

Please add an extra property to the general tab of an item:

"Multiple-feedback-handeling"


This property has at least the following options:

LTP (default) = last takes priority  (So last changed feedback sets value/text of the item. This is current behavior)

HTP = Highest takes priority

OR

AND

NOR

SUM

This way, when developer does not change the property it will work as before and all others can set the behavior they need.


In my case: I needed to have an error indicator that has 10 inputs that are 1 if no error and go to 0 when there is an error for that input. So I ended up writing Javascript to combine al these inputs to one project token "error". I had to subscribe to tagchanges for the 10 inputs, etc etc.

Much easier would be to drag the 10 inputs to my error-button as feedback and then set the new Multiple-feedback-handeling property of my button to "AND".

OK, so such option is not available yet.

Is the way I do it now the best way? Or would I be better of using schemes? Or is there another better/easier way?