08-28-2006 10:40 AM - edited 08-28-2006 10:40 AM
Message Edited by Darren on 08-28-2006 10:40 AM
08-28-2006 02:11 PM
08-28-2006 02:26 PM
For the case of identical parent paths, it does act like a string comparison, so yes, "c:\blah314.txt" would be in the range of "c:\blah1.txt" to "c:\blah5.txt".
For a more deeply nested path, I believe it compares byte-by-byte. So "c:\blah\heyyou.txt" would in the range of "c:\a.txt" and "c:\c.txt".
Hope this helps,
08-28-2006 05:04 PM
Sure !.. need 1 g of acetylsalicilic acid now...
Darren a écrit: ... Hope this helps,
08-28-2006 07:36 PM
The more I learn, the less I know... -sigh-
I never suspected that the range & coherce could (or would ever) work for paths.
08-30-2006 06:26 AM
[...] As you can see, the value of "c:\blah4.txt" is determined to be "in range", i.e. in between the values "c:\blah1.txt" and "c:\blah5.txt". I don't know when I would possibly use this behavior, but it's nice to know it's there.
I could imagine a scenario with VIs myVI_1.00.vi, myVI_1.01.vi, myVI_1.02.vi ... of different versions that are located in the same directory and wait to become loaded dynamically. Inside a possible caller, set the borders of the coerce function programmatically to the highest/lowest available VIs (assuming subsequent VI versions are all available) and the caller gets a VI loaded - whether requesting a VI name in range of the available VIs or a newer/older version that ist not there.
May sound a bit academic, but it can easily achieve some cool "injection" abilities of testing newer/older VIs without changing the caller's code, if this itself is prepared to handle dynamic VI calls! I know this could be achieved with other comparison functions, too - but one can say the same with the coerce function itself.
08-30-2006 10:19 AM
08-30-2006 10:31 AM
09-03-2006 08:03 AM
LabVIEW, C'est LabVIEW