LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

upgrading from 8.61 to 2010 labview write string adds white spaces to both sides of the = sign

upgrading from 8.61 to 2010 labview write string adds white spaces to both sides of the =  sign insted of Key=Value in LV8.61, 2010 write Key = Value

0 Kudos
Message 1 of 7
(2,667 Views)

Hi 321,

 

yes, the ConfigurationFile functions changed a little bit in the mean time...

 

But:

Is it a problem for you? Or do you only want to express the need for reading the "Upgrade notes" manual?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 7
(2,659 Views)

If it is a problem, then that implies you're trying to parse the file manually instead of using the configuration VIs. Is this what you are doing?

 

It should also be noted that the INI file format is not well defined, so having spaces around the equal sign is not, in and of itself, "wrong".

0 Kudos
Message 3 of 7
(2,639 Views)

its a problem for me as when this code was written LV did not have these methods and my legacy code worked in LV8.6, but now reqires re-writing after updating to LV 2010

0 Kudos
Message 4 of 7
(2,628 Views)

 


@321 wrote:

its a problem for me as when this code was written LV did not have these methods and my legacy code worked in LV8.6, but now reqires re-writing after updating to LV 2010


I don't understand what you are referring to. The Configuration File VIs have existed for a long time, well before 8.6.

 

0 Kudos
Message 5 of 7
(2,625 Views)

Legacy code in LV4 the point is it worked before the white spaces were added

0 Kudos
Message 6 of 7
(2,620 Views)

So are you saying that you're trying to read a config file that was written with LabVIEW 2010 with code that was written in LabVIEW 4?

 

If so, then you need to fix the LabVIEW 4 software, not change LabVIEW 2010, since it's not really doing anything wrong. The same exact thing would happen if the config file was written by another program that just happened to put spaces around the equal sign, or the file was edited manually by someone who likes spaces around the equal sign.

 

If that's not what you're doing, then please explain the specific issue because I don't get it then.

0 Kudos
Message 7 of 7
(2,611 Views)