A long explanation :-( ....
The API is sending messages received from the Cortex internal communication network. That is the messages being transfered from one object to another. This is defined by the connections.
In addition to the connections set-up by the user in the connections menus (static) their are also temporary connections made by the system (dynamic). For example if you have an intercom session, the cancel buttons on all panels have dynamic connections made to the 'All intercom object' to cancel a session. The cancel buttons are then released for another task at the end of a session.
The Infrared receiver can be used to mimic the buttons on a panel. So you can sit in your arm chair and operated the panel and navigate menus etc. The buttons are no longer working directly how they are configured in the connections menu but all the buttons actions are steared towards a User defined Menu. The buttons are actioning their dynamic connections.
So the bottom line is that the output of many objects will trigger their normal connections (static as set by user) and if applicable their dynamic connections (as reconfigured temporarily by the system).
The API is tied into this interface and is seeing both static and dynamic 'pings'.
I think it is not appropriate that the API sees the dynamic pings and we will change it in future updates.
So the simple answer to you question is yes they are redundant.
Viv.



Reply With Quote

