Display tokens in text file

[Hannamon]

Hello All;

I am working on some text file update VI's, and I am having quite a bit of trouble with tokens...

In order to get all my offsets and such correct, I need to input a text file (using Read From Text File), but I want to display all tokens with the text. I've played around with the Scan String for Tokens VI, but cannot get it to do what I want it to.

I am attaching a sample text file.  Is there a quick way of doing this?  (i.e. read from file, put into string, scan entire string and output same string with both text and tokens visible)...

Thanks.

D. J. Hanna

[GerdW]

Hi Hannamon,

your example text file cries for using "config file" (aka ini-file) functions! They can be found in their own subfolder of the file palette...
And there are some examples coming with LabView too! (Search for "configuration".)

Message Edited by GerdW on 10-25-2007 03:41 PM

[Hannamon]

Hi All;

True, I did create the original text file using the Config File VIs, however! my need for a text file editor has outgrown their usefulness; perhaps I should have explained my full application intent:

I have a text-based configuration file that is used by multiple software platforms, and is already in existence.  I am not versed in these platforms, and so my platform of choice is LabVIEW.  I need to pull certain configuration and variable information from these text-based files and use them in my LabVIEW application.  These text-based files are set up in a format significantly different that would be useful in a Config VI, and I do not have the option of reformatting the text-based file to suit my needs.  Think of it as a "one text-file format for all applications" type of idea.

Hence the need to identify the string tokens as part of my original post.  (GerdW: normally a good idea, I agree!  But I hope my explanation clarifies my current need.)

DJH

[GerdW]

Hi Hannamon,

then you shouldn't attach a text file that definitely looks like an ini-file
When you can't use the config file functions you have to program all their possibilieties on your own

Well, I would try to use the string functions (like Scan from string, Match pattern, Spreadsheet string to array,...).
See the attachment to get a clue.

[Hannamon]

Thanks, GerdW;

Sorry about the initial confusion; for me it was more of a "next logical step" from config vi to a general text file reader 😉

I think the spreadsheet string to array.vi will probably be an easier route for me to go, since each line item contains system information, and I can just parse it accordingly!  I'll give it a go, and update the thread on my progress.  Thanks for the example!

Regards,

D. J. Hanna

[Hannamon]

Just to close out the thread, the Spreadsheet String to Array turned out to be what I needed... this handled the eol quite nicely, and I only had to reverse the process to write the file.  Thanks!

DJH