Your comments

Thanks Vladimir, I have tested again with my project running on the latest server release and did not get it working as expected. All virtual feedbacks were still empty after each server reboot.

Then I made a new simple testproject with only 1 persistant virtual command forwarded to a virtual feedback, just to show you what settings I was using. To my surprise in this sample-project (with exact same settings) persistency worked perfect.

Then for further testing I added one more virtual command/feedback combination to my main project. This new variable kept it's value after reboot (exact same settings as the P1_Capacity variable mentioned above), but the old onces still did not persist.

At that time, I decided to delete all old persistant variables and just recreate them with exact same names and properties.

So I guess there was something wrong in the way these variables were stored in the serverprojectfile, that could only be fixed this way.

Can some admin please moderate this posting, so other users can respond?

That does exactly what it says.

After that I can still select "SCHEMES":

Hi Aleksandr,

Right now, Studio does not allow adding  Schemes to an Panel project anymore..... at least, the add button does not work anymore. There is no error message or other info :-(  That is quite annoying about Iridium in general: sometimes things don't work as can be expected, but there is no good feedback to the user about this from the program.

The SCHEMES panel is still visible in a panel-project:

iRidium Environment:

iRidium Studio: (64 bit)

Transfer: (32 bit)

iRidium: (64 bit)

Server: (32 bit)

iRidium lite: (32 bit)

Server lite: (32 bit)

I just found out Schemes does not work on a Panel-project, so that is not the way to go either ......

Why does Iridium Studio allow making Schemes in a Panel project if they don't work anyway? And why do I not get an error message?

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:


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





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?