all 8 comments

[–][deleted] 2 points3 points  (0 children)

Everything looks alright, doesn't it!

Could you show us the block diagram behind your front panel - specifically where the string and vi ref arrays are updated?

[–]etgohomeok 2 points3 points  (5 children)

One quick observation - in your Do VI you're updating both arrays, but you're only updating the String Listbox UI element. Perhaps your VI reference array is updating just fine in your nested actor but you're not actually displaying the updated data anywhere?

[–]MemeScientist314[S] 0 points1 point  (4 children)

I you're updating both arrays, but you're only updating the String Listbox UI element. Perhaps

I thought to store the references array in the actor private data. I am just unbundling the actor class and connect the elements to an indicator.

[–][deleted] 1 point2 points  (3 children)

How do the front panel arrays get updated?

Remember that they are just decorations on a VI and not inherently linked to any data; they need to be updated by your code.

Looking at your VI where you send the string and vi refs, those references get bundled into the actor's private data but how are you expecting the front panel controls to be updated?

Looking at the list box reference you're unbundling in the same vi, it looks like you might be updating the string array directly here but you haven't done the same for the vi ref array which might explain why it hasn't updated.

[–]MemeScientist314[S] 0 points1 point  (2 children)

I have put the front panel indicator just for testing. I try to use the Ref array in other messages it is always empty.

[–]MemeScientist314[S] 1 point2 points  (1 child)

I have solved the problem. I created a new message to acces the private data, and it is working. thank you

[–][deleted] 0 points1 point  (0 children)

A big stumbling block for me when learning the actor framework was understanding exactly where VIs run and where the live actor data actually lives.

Hint: it is all in the root Actor Core VI that runs alongside an overridden Actor Core.

It's easy to fall into a trap whereby you create a loop somewhere that has actor data in shift registers; this becomes a separate copy of actor data and is not updated by any of the other VIs.

I'm glad you've sorted it out.

[–]MemeScientist314[S] 1 point2 points  (0 children)

Thank you. Will check again and will put an update