Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 01/17/2012 in all areas

  1. This OpenG Review is closed. See Summary Post here. Please start a new thread to discuss new changes to this VI. Read this post for start of review. I’d like to suggest these three VIs (or similar) as possible LVOOP-object additions to the OpenG Toolkit: “Get Class Name” is a modification of “Get Name of Class of Object” posted by AQ. Here it just returns the basic class name (which I use often in custom probes and the like). "Get Default Object” is inspired by this discussion and uses AQ’s zero-iteration loop method. This is a very simple VI, but using it instead of the raw code is much clearer to the reader. “Same or child class” just uses “Preserve Runtime Class” as a tester. Again, the advantage here is code readability (or it will be, as soon as someone comes up with a good icon for it). Thoughts? — James OpenG Suggestions.zip
    3 points
  2. No, it preserves the wire type, so no need to "cast back”: There are stronger arguments against “Same Class” than “Same or Child”. Also, with the above suggested OpenG VIs, one can build “Same Class” functionality in a clearer way (Is the default type of each object the same? —> Same class, for example). — James BTW, what do people think about error terminals on any of these VIs? I’ve left them off.
    1 point
  3. I don't recognize any of the authors off-hand, but I would at least the first three topics good for general-purpose integration knowledge. The last two seem like they could be vague wrt a specific application, but on the balance it seems like there would be useful information. $100USD is rather steep for a casual read, though.
    1 point
  4. I would use this approach. It is fast and reliable.
    1 point
  5. Suggestion: Shouldn’t the “Get Name of Class of Object” VI get a default value of the object before flattening it? Since you don’t need the actual data flattened and it could take a long time if the object data is very large.
    1 point
  6. I would suggest you check out the localization toolkit on the LabVIEW Tools Network: http://sine.ni.com/nips/cds/view/p/lang/en/nid/209037 They have an evaluation version you could try. It's a very nice tool.
    1 point
×
×
  • Create New...

Important Information

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