Current Behavior of LabVIEW
Currently, the error messages that emerge from bad call to a Property Node or Invoke Node only state that the error occurred in a property node or invoke node.
User Need
As a user of LabVIEW, it saves me considerable time in development/debugging, when I can precisely know why and where in the code an error occurred , so that I can get on with the actual work of fixing the bug in my own code/logic.
Problem For Users
The current behavior, described above, makes it impossible to know (without placing probes and retaining wire values):
A) Which Property Node or Invoke Node actually generated the error (in cases where there are many of such nodes)? Again, all we know is that some Property/Invoke Node on the block diagram of the VI raised the error.
B) Which specific Property actually caused the error, in cases where a Property Node has multiple properties that it is reading and/or writing. Again, all we know is that the error occurred inside a Property Node.
Proposed Solution
Error message for invoke/property nodes should state:
- the Name of the Method or Property where the error occurred
- the Class Name of the VI Server Object (if available)
- the Object Refnum value (e.g. the hex value of the object reference)
- possibly even (only if running in the editor and not the runtime environment) the VI Server Scripting UID of the GObject node on the Block Diagram for super-fast debugging with a "fancy error dialog of the future" (TM) whose LV Idea Exchange post with undoubtedly be coming soon...