Thread: Using Tables in LabView.
View Single Post
  #3   Spotlight this post!  
Unread 15-03-2009, 10:55
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
  
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Using Tables in LabView.
To continue filling in the info. Arrays are the datatype oriented control. An array of strings can be one, two, or multi-dimensional. It allows for decent editing, but not great. A table in LV always has a 2D array of string as the datatype, and it is the editing interface that improves -- still not Excel on a panel, but better. The listbox may seem odd because its datatype isn't string at all, but numeric. It is more for displaying a selection to the user and letting them choose a single or a set of items from a list. You can then read the properties to see what the strings were, or you can just know what you put there. Then you can index the array using the selection index. Beware that RT isn't really meant for doing interfaces. Some of the UI things work, but not all. Be sure to test and don't be totally surprised when UI centric things don't work on RT.

Greg McKaskle
Reply With Quote