11-19-2006 01:38 AM
11-20-2006 04:09 AM
As for references to array elements, we have tried something:
http://forums.ni.com/ni/board/message?board.id=170&message.id=213030
11-20-2006 04:29 AM
Hi - i attached you here a screenshot about the attached SetClusterArrayElement.vi - where you see how connected property node to the array of cluster of the frontpanel - you set a new property node from blockdiagramm pallett -> applications control menu and rightclick to property node, then connect/link to and then select here the cluster element/reference like in screenshot. Run the SetClusterElement.vi and you see how yout set the new values programmatically...
Hope this help you. Please let me know if it solve your problem
Best Regards AE Munich
11-20-2006 05:39 AM
Hi,
thanks for the help. The problem is: You use a cluster and put in arrays. What I would like to do is to use an array and put in a cluster with different frontpanelelements.
But your help brought me on the right track.
I attached my example. The problem is: as long as the cursor is in the first array element it works fine (e.g. if I set the cursor in the first numeric field in the first array element, or in the string element of the first array element)) - if i set the cursor in the last element, I only get the value of the last element.
Do you have an idee, how I can solve this problem?
Kind regards,
Frank
11-20-2006 07:04 AM
In the discussion i linked above, we have solved the problem by making the array 1 element wide (only 1 element is shown at a time). This way the cursor is always there!
If you need to show the array, then create a copy of it. Make the original array (the one you write to) invisible, and after every update copy its content to the other array (the visible one).
11-20-2006 07:07 AM
Hi,
thanks! That sould do it! Perfect!!
Kind regards,
Frank
11-20-2006 08:12 AM
11-21-2006 02:20 AM
Ahem, no, that's not the solution ![]()
Focus stays on the last slot you clicked. Try to click the 3rd visible element, and it will always update the 3rd visible element, no matter how you shift the array. ArrElem.KeyFocus does not do the trick, that's why we needed the 1-slot array