We'll have a look at that - normally the path would auto-create if it didn't exist, but might not be working in this instance
It outputs the current values at the time you make the call, so if you want to record the values every second, setup the rule with unlimited triggers rearming one second apart.
What are you using to parse it? Is it something that expects repeating blocks of multiple rows?jimibt wrote: ↑Wed Jul 22, 2020 11:04 amSo, one further question. Altho I could PARSE the file and format it into the structure I require, would it be possible to have an option to put each selection on its own line.
Presently, all sv's per call are displayed on a single line which makes any functional use of them a bit limited
The idea was that every call would go on a new line and then they would export in a predictable order. This format is ideal for plotting a chart or analysing with Excel as all the values will go down a column without having to skip rows.
If you're writing the parsing code by hand then each section type tells you how many name/value pairs are in it, so its easy to skip x * 2 columns to get to the new section.
I'm not saying we won't add another export option, just want to understand what you're using to parse it that requires repeating blocks of data. The rule originally started life as a debug facility used just to keep track of current values of things!