Not a path

[AKA_TG]

Watch out for this one guys, although it is easy enough to work around.

Its on 2010 and 2009, perhaps further back as well.

[RavensFan]

Are you claiming a bug?  Or just a point out something that caught you off guard?

The results of the VI are accurate.

In the top you used a Not a Path constant, checked it for "not a path" and the result is true.

In the top you used the same constant, and converted it to a string.  The string is empty.  Converted it back to a path.  Now you do have a path, it just happens to be an empty path, so when you evaluate it for Not a Path, the result is false.

An empty path and a Not a Path are two different things.  But you lose that information when you convert it to a string datatype.

[AKA_TG]

I agree.

It actually caught me off guard because it was easy to think that conversions would produce the same result when reversed.

[AKA_TG]

What I meant to say is

now that you explain it that way I agree it is not a bug

Thanks!