mariokom
mariokom
I agree that the ASAPI's set|getComponentProperty are unecessary. I will add the new functions with the names you 've proposed. With this addition - and if a plugin is implemented...
Hi Martin, Sorry in advance if the following response is too technical :) Actually, this is not what i wanted to achieve. My scenario is **to change the variable from...
Forgot to mention that the changes are part of a P4All deliverable which must be submitted before the 10nth of July. Do we plan the next release before or after...
Ok lets move this conversation on skype. No i was not planning to implement it for 2.8 (i can sense a small panic attack just by mentioning it :p )....
We currently support "ARE events" (deploy, start, pause, resume, stop). By "model events" i am reffering to the events produced (in a specific model) during runtime. Quoting an old email...
Model events are now delivered via the SSE mechanism, along with channel data and runtime component property changes
Glad it worked for you Martin :) Yes i understand your point and it is - semantically speaking - better to register on ports. A componentXX_portXX name is also more...
@deinhofer : Yes this is what i ment by saying that they have to be connected with a channel. I am already making modifications to make it work with ports...