Leaderboard

There's a VI in the lvdata package called Get Default Data from TD (that accepts a type descriptor input), but there's no equivalent (wrapper) for variant data input. I suggest that a Get Default Data from Variant VI be added to the library, for symmetry (and the fact that it would be useful -- I've needed such a function recently). Get Default Data from Variant.vi

Don't say I didn't tell you a way to make it faster. Personally I would not use subroutine priority in either case, I typically am satisfied with disabling debugging. I do however benchmark code using that setting, I found it to be the fairest and most consistent comparison. In completed code, I almost always find myself wanting to run subVIs standalone at some point.

Ok here is the updated candidate thanks to the improvements made by Darin and Fab. Included in the ZIP is the benchmarking VI Darin mentions. To Character Array.vi To Character Array.zip Code in LabVIEW 2009

Hey Guys, that's great! On the topic of execution priority - I am not sure we want to this set as subroutine priority like we did with the Trim Whitespace change. One of the reasons we did this was that NI's Trim Whitespace uses that setting: I think this setting should be reserved for special cases only. When do you use Subroutine priority? is a LAVA thread that Jim pointed me too. Feel free to chime in there too with your experiences. Of course please discuss in this thread if you think To Character Array should use this setting (highlighting pros and cons is helpful).

I find the VI useful and I think it should be part of OpenG. I made the following modifications for speed: But when I benchmark it some times it is faster, but some times it is not. It seems that the original version is more consistent: Original code: Modified code: I am attaching the Benchmark VIs I used: TEST - To Character Array-modified.vi BenchMark-To Character Array-modified.vi BenchMark-To Character Array.vi Fab I guess I need to learn to post a lot faster !!! But hey, great minds think a like