09-10-2001 09:08 AM
09-10-2001 09:27 AM
09-17-2009 01:19 AM
Hi Dennis, writing key updates or add lines, but the problem is that it also causes all lines to be clumped together, making it unreadable.
What's the better way?
Clement
09-17-2009 01:31 PM
To Original Poster: Be careful about using the Current VI Path function: Why Does My Executable Not Work When Using the Current VI's Path Constant?
astroboy wrote:Hi Dennis, writing key updates or add lines, but the problem is that it also causes all lines to be clumped together, making it unreadable.
By "clumped together" are you referring to linefeeds being removed? Yeah, that's annoying isn't it? Unfortunately, that's what you get with the stock config VIs.
09-17-2009 09:26 PM - edited 09-17-2009 09:29 PM
astroboy wrote:Hi Dennis, writing key updates or add lines, but the problem is that it also causes all lines to be clumped together, making it unreadable.
What's the better way?
Clement
I was complaining about the poor formatting of the .ini files myself a couple years ago in this thread. http://forums.ni.com/ni/board/message?board.id=170&message.id=273552
I found the offending piece of code was buried pretty deep in the Config File VI hierarchy.
One idea is to go back after the file is written and find where all the section headers are and insert your own blank lines.
Also look at this thread http://forums.ni.com/ni/board/message?board.id=170&view=by_date_ascending&message.id=408776
You may also want to add kudoes to the config file idea in the Idea board. http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Comments-in-configuration-file-ini/idi-p/927874#A614