Jump to content

crelf

Members
  • Posts

    5,759
  • Joined

  • Last visited

  • Days Won

    55

Everything posted by crelf

  1. QUOTE (Cat @ Apr 3 2009, 08:32 AM) If you like that, then you'll love http://forums.lavag.org/LVSpeak-tell-LV-what-to-do-t13687.html' target="_blank">LVSpeak. I figure it would really help those without the dexterity to control a tactile input device.
  2. The "get pizza" command is freaking hillarious!
  3. QUOTE (ASTDan @ Mar 31 2009, 11:24 AM) Only if they're made from hemp
  4. QUOTE (ASTDan @ Mar 30 2009, 07:54 PM) Ahhh - but wasting unproductive brain cells is an ends-justifies-the-means and for-the-greater-good realization: http://hubpages.com/forum/topic/9591
  5. crelf

    Alfa String

    QUOTE (alfa @ Mar 28 2009, 03:55 AM) I'll save the lambs by smuggling them out in my belly I'll stop eating lamb when it stops tasting so damn good.
  6. I don't care whether you agree that climate change is true or not, I can't think of any time that it's a good idea to waste energy. Heck, I don't think it's a good idea to waste *anything*.
  7. QUOTE (xuniL @ Mar 23 2009, 04:13 PM) Geek-out about the innovative LabVIEW stuff you're doing, not the boring server stuff that someone else can do. Seriously - if you try to do it yourself, you'll likely forget something and loose everything, or you'll implement a server architecture that's fine for now, but doesn't allow you to grow (meaning pain in the medium to long term).
  8. QUOTE (Matthew Zaleski @ Mar 21 2009, 07:28 PM) :thumbup: I learned the framework of every bit and every clock cycle counts. Whilst it helps me occasionally, I used to really get hung up on it. Now, I prefer to be productive.
  9. This topic is now closed - the submission has been accepted into the LAVAcr - see here for more details.
  10. QUOTE (flarn2006 @ Mar 21 2009, 01:00 PM) There's a scripting toolkit in the LAVA Code Repository that might help.
  11. QUOTE (Ton @ Mar 19 2009, 04:07 PM) I'm already there.
  12. QUOTE (PaulG. @ Mar 19 2009, 01:37 PM) Embrace open source, or be left behind. Open source is the future.
  13. QUOTE (Norm Kirchner @ Mar 15 2009, 05:09 PM) You had me until you mentioned camping. I wonder if NI could let us use a conference room for a couple of days? Might also be a good time for those presenting at NI-Week to practise their sessions in front of their peers...
  14. crelf

    NIWeek Beer tally

    As a thank you for their great support here on LAVA, a lot of members have been promising each other to buy them a beer at NI-Week. This thread is to try to keep track of those. How it works: If you owe someone a beer, make a new post. Then, if you owe someone else a beer, edit your post and add them to your list. If all goes well, you'll have a running tally of how empty your pockets are going to be in August
  15. This is the place to discuss anything and everything NI-Week 2009. Sessions you're interested in, parties you're inviting members to, the LAVA/OpenG BBQ, photos from 6th street - you name it, post it here.
  16. QUOTE (Yair @ Mar 15 2009, 02:15 PM) Ohhh - I see what you're saying now - you're saying that you'd want something that you could put multiple subVIs/primatives in, and in that case I agree that using a one page sequence structure is the way to go. What I was suggesting was never meant to replace that behaviour. QUOTE (Yair @ Mar 15 2009, 02:15 PM) I simply fail to see the big advantage in having a "special" wire and I do see potential for problems. For the record, I'm not crazy about the special wire either, and that's why I suggested the "Visible Items > Sequence Container".
  17. QUOTE (Yair @ Mar 15 2009, 12:59 PM) I thought I'd already done that - can you help me to understand what you're looking for?
  18. QUOTE (jgcode @ Mar 15 2009, 04:38 AM) jgcode's right - show us your code.
  19. QUOTE (crelf @ Mar 7 2009, 02:50 PM) Now it's down to $598!
  20. QUOTE (Jim Kring @ Mar 14 2009, 05:06 PM) What's not to understand? It's a new method of forcing and dsiplaying execution order when we can't use dataflow (easily or neatly). QUOTE (Yair @ Mar 14 2009, 12:12 PM) I think this is a terrible idea and would create a huge potential for wiring bugs for people who won't notice the border or know what it is. I'm guessing that you just want the users of the NI forums to have more threads they'll need to respond to. I'm not married to the visual implementation. QUOTE (Yair @ Mar 14 2009, 12:12 PM) You would essentially have to wire to every data flow "start" and "end" points within the tested piece of code. Just like we currently do with dataflow? QUOTE (Yair @ Mar 14 2009, 12:12 PM) If you guys don't like the sequence structure because of its size, all you need to do is use the diagram disable structure which has a much thinner border and which I believe can have a single frame. Yuk! That'd be unintuative - people looking at code like that would see a diagram disable structure. Sure, there are ways around this issue, but we're discussing an intuative new feature.
  21. QUOTE (Dan DeFriese @ Mar 13 2009, 03:25 PM) :thumbup:
  22. QUOTE (FLAnatic @ Mar 13 2009, 01:21 PM) Omniscient, omnipotent, impotent - it's all the same, right?
  23. QUOTE (shoneill @ Mar 12 2009, 03:28 PM) How about this: QUOTE (Mark Yedinak @ Mar 12 2009, 03:35 PM) Essentially we are both suggesting the same thing with the exception that your suggestion would allow you to use any wire to control the sequence whereas mine would require the Null wire. Right. Would this other idea preclude the existance of the null wire? (As long as every VI/primitave has at least one output to be able to control dataflow...) ...and I'm sure the NI R&D legends would be able to make optimizations in the compiler that strip out the data from such a wire if they detect that it's only sinks are these sequencing containers (maybe that's the way it already works with sequence structures? If not, it might be a good idea )
  24. QUOTE (TG @ Mar 12 2009, 12:06 PM) That's a good idea - or maybe you could right-click on a VI/primitive and select "Visible Items > Sequence Container" which would add a 3 pixel border around the VI/primitive that we can wire any datatype to. Then it'd be obvious which wires are for dataflow only and which ones are connected to the connector pane.
  25. QUOTE (menghuihantang @ Mar 12 2009, 12:59 PM) Search the LabVIEW help for "LabVIEW Style Checklist" - that's what you're being graded by.
×
×
  • Create New...

Important Information

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