Bug in LV2020 scan relative time

[thols]

In LV2019, Scan from string can be set to "%t" and scan a relative time string of e.g. 12:34:56, but in LV2020, that doesn't work:

Try attached VI in LV2020 vs an earlier LV version and see. 

Or am I missing something?

[WaiLee]

Hi thols,

It actually work.

You have to follow the correct format for the input string below in order to get your output:

I'm using LV 2020 too.

[thols]

Sure, but can you figure out why the string "12:34:56" works in 2019 but not 2020?

[WaiLee]

 I think LabVIEW 2020 had updated some features and emphasised on the complete writing format for the format ' %t ' which must included the date.

[billko]

There was a similar issue I uncovered a while back where scan from string worked a little differently.  I think it was a jump from LV 2012 to LV 2015.  Somewhere in between LV 2015 and LV 2018, it changed the way it treated spaces that came right before numbers and my parsing no longer worked.

[thols]

So, is this a bug or an undocumented feature that was trimmed out? I cannot actually find any exact mentioning of that format in the documentation. Shouldn't more people have stumbled upon this? I mean, %t seems pretty natural to try on that string.

The documentation I can find is pretty sparse on "t" as a conversion code, it really only refers to the examples, and the examples does not contain that exact string:

[urs.sieg]

Hi thols,

i jumped over the same problem. I think it's not about giving the whole date but more about giving decimal seconds. 

1:23:45.6 will work.

Such undocumented changes from one LabView versions to another is quite unexpected and thus hard to debug. 

cheers

urs