Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

Hello everyone,

First, I needed to set a data in the trig from the actor. I got this part done with IVFSNODE_SetData().

Now, I need to notify that node so anyone who is observing that variable can update... How would I do this?

IVFSNODE_Notify() takes in a IVfsNode* and it seems there is no way to just create a node from VfsPathElement.

If there is no way to do it, can I just notify the root? What would be the reasons not to do it besides the performance issue?

Thanks!

Rock Lee wrote:First, I needed to set a data in the trig from the actor. I got this part done with IVFSNODE_SetData().Why not use an actor node(R/W) instead of a variable??
Rock Lee wrote:IVFSNODE_Notify() takes in a IVfsNode* and it seems there is no way to just create a node from VfsPathElement.Dont think if this is possible..??? :confused: :confused: Need to investigate...
The variables are observed during trig life time if automatic observation is activated.
So the code below should work in case of change in variable value. [Might have some side effects, i think this code will be invoked everytime we parse the DOM tree]...Of course you need to know what all values will be set.. Else some other logic has to be used. I suggest you use an actor node for this.. No confusion ... :D

Rock Lee wrote:First, I needed to set a data in the trig from the actor. I got this part done with IVFSNODE_SetData().Why not use an actor node(R/W) instead of a variable??
Rock Lee wrote:IVFSNODE_Notify() takes in a IVfsNode* and it seems there is no way to just create a node from VfsPathElement.Dont think if this is possible..??? :confused: :confused: Need to investigate...
The variables are observed during trig life time if automatic observation is activated.
So the code below should work in case of change in variable value. [Might have some side effects, i think this code will be invoked everytime we parse the DOM tree]...Of course you need to know what all values will be set.. Else some other logic has to be used. I suggest you use an actor node for this.. No confusion ... :D

Hey Oceans,
Thanks again, but I ended up sending an event and argument to elem/_root instead.

Hey Oceans,
Thanks again, but I ended up sending an event and argument to elem/_root instead.

Rock Lee wrote:Hey Oceans,
Thanks again, but I ended up sending an event and argument to elem/_root instead.Yup thats also a good idea.. i forgot to mention that...

Rock Lee wrote:Hey Oceans,
Thanks again, but I ended up sending an event and argument to elem/_root instead.Yup thats also a good idea.. i forgot to mention that...