View Single Post
  #3   Spotlight this post!  
Unread 01-02-2013, 08:03
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: Setting and saving values on Dashboard

The white paper introduces the ini VIs, or the Config VIs I think they are called. As you said, XML, a text file, or even a binary file will work. I chose the ini file for the driver station and dashboard for the occasions when people want to view or edit it by hand. People may claim that XML is human readable, but not by normal humans.

The biggest difference in the approaches is that XML can encode more data types than ini, but ini is more human readable.

The other axis of this is how you read and write to the controls and indicators. You can use locals, value properties, or even VI server methods that are name and variant based. In my opinion, it is really a personal preference as to which to use. All of them work fine. The value and method allow the code to go into a subVI and are therefore more compact and more extensible, but are initially a bit harder to read and somewhat more brittle when things change.

Greg McKaskle
Reply With Quote