Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 10/07/2011 in all areas

  1. Here is my favorite mathmatical identity: I now have a second favorite: What has been seen can't be unseen...
    5 points
  2. I just set the block diagram background colour in the preferences. I use a different colour for each LV version so I'm aware of what version I'm in. I also use it as a "completion" indicator". I start out with all the diagram in a colour and set cases, frames etc it back to white once that frame/module or whatever is completed. That way I (or my colleagues) can see at a glance where I need to do some more work. Yes. It sticks with the vi.
    1 point
  3. I think we all agree on the functionality of the VIs which is good. The only functionality I am unsure of is this: IMO: If you want to clear all errors then you should use the Clear Errors VI. If an empty Error Code Array is passed in, then it contains no Error Codes and therefore no Errors should be cleared? Ok, here is the API I am envisaging... I have gone with the standard size/shape VI given that other Error VIs are of this size (Clear Errors, Merge Errors, Build Error Cluster etc...) It seems to me even an inline VI size/shape would still get in the way of the outputs of the Property Nodes anyway? E.g. The core VIs: The thin wrappers for Error Array support: The Polymorphic API: Documentation: Here are some examples of inputs/outputs of the API: Here are the results: Clear Specific Error.zip Code is in LabVIEW 2009
    1 point
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.