(If this is the wrong repo, let me know. It's not perfectly clear yet to me where this goes.)
Hands-On 2 says:
: If the configuration file name is not valid you will receive error 538500
And for that error number, the LabVIEW error text is:
Class not found
Can we catch that error if there's no valid config file, and return something like "No config file found" to the user instead? The default execution template exhibits this behavior like the examples.
There's enough new stuff going on while getting your feet wet with DCAF that a bad error description like that can be a bit jarring for a new user. (It's worth noting that in the Hands On, the first time the new user could run into this is right after the discussion of the scripted Includes.vi . That leaves the user wanting to jump down that rabbit hole if the classes aren't found.)
(If this is the wrong repo, let me know. It's not perfectly clear yet to me where this goes.)
Hands-On 2 says:
And for that error number, the LabVIEW error text is:
Can we catch that error if there's no valid config file, and return something like "No config file found" to the user instead? The default execution template exhibits this behavior like the examples.
There's enough new stuff going on while getting your feet wet with DCAF that a bad error description like that can be a bit jarring for a new user. (It's worth noting that in the Hands On, the first time the new user could run into this is right after the discussion of the scripted Includes.vi . That leaves the user wanting to jump down that rabbit hole if the classes aren't found.)