Jump to content

crelf

Members
  • Posts

    5,759
  • Joined

  • Last visited

  • Days Won

    55

Everything posted by crelf

  1. Cool Tool - "infoEnum (enum type definition browser)" - download & discuss http://tinyurl.com/3t5oyws

  2. Should #lava add a "Patent Watch" forum? http://tinyurl.com/3gmdgnd

  3. Ummm, it's called dataflow Your subVI has the IO constant as an input (which is an output of the case structure), and the error out (which is an input of the case structure). The case can't execute until it has data at all of its input tunnels, and it can't satisfy that for the error cluster.
  4. Your bit-twiddling brain teaser for the day: http://tinyurl.com/42dfoe2

  5. Neat #labview tool - "UI Skin" - Download & Discuss: http://tinyurl.com/3vaqvu7

  6. Sounds like you want the source code to the VIE Documentation Generator
  7. OpenG to the rescue! Programmatically Write/Read control and indicator values to/from human-readale file - http://tinyurl.com/3jgl7cs

  8. OpenG has some awesome VIs that write/read control/indicator values to/from disk (human readable ini files).
  9. I remember someone made a text to picture VI once that allowed you to do all sorts of stuff, including setting a rotation angle.
  10. Filtering #labview Shared Variable Value Change Events http://tinyurl.com/3vdog9a

  11. RT @eyesonvis: I have an idea for the LAVA NIWeek t-shirt. Part of the design is a VI diagram. What should the VI do? Something simple/funny

  12. Me too, but I'd probably just use it to work more. So, in a way, I guess I do
  13. Awesome new #labview wiki page: LabVIEW's decision tree when loading a vi into memory from disk http://labviewwiki.org/Loading_vis

  14. No. In fact, I think it's unintuative and will make the dissemination of code even more difficult in the community. From what I can tell, what you're trying to do is collect some reusable components/modules/architectures based on the fact that they're in snippet form - so limiting a code repository to only one very limited filetype in LabVIEW is, IMHO, a step backwards. As already mentioned, snippets are too basic for architectural reuse, but there's also already many other more appropriate places for this type of reuse that's more targeted (things that ship with LabVIEW, OpenG, ni.com, LAVA, etc - ppl can alreay post snippets. VIs, zips, vipcs, etc there, so why give them a new place where they can only post one tyep?). I'm trying not be negative, but I think that the addition of a new site would just mean that I need to search another place for something I'm looking for.
  15. If your code includes requirements tage (like the [REQ: xx-xxxx] type) on the diagrams and/or VI despcriptions, you could use scripting (and/or NI Requirements Gateway) to create a list.
  16. I don't use them often, although a lot of my work is in 2009.
  17. It's a known issue - we're working on it. Ah - that's what you were talking about! Sorry, I thought you were saying LAVA was down - that's different.
  18. You input needed! New Flexible GUI application - download & discuss: http://tinyurl.com/3o7fhgo

  19. Yes, and yes. Seriously though, there just aren't that many places within walking distance of the ACC that could accomodate us. The general consensus at last year's BBQ (which may have been fuelled by beer) was that it was good and that we should have it there again this year.
  20. I just bought my ticket - post here when you buy yours!
  21. LAVA/OpenG NIWeek 2011 Bar-B-Que TICKETS ON SALE! http://tinyurl.com/3j6c63y

  22. DVR{LVOOP} creation - don't forget to check the inheritance properties for your class: http://tinyurl.com/3gd5rg2

×
×
  • Create New...

Important Information

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