Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 12/20/2012 in all areas

  1. If you have any interest in language design, graphical or textual (because in this case they're hard to separate), you may enjoy reading this article. It contains some very inspirational concepts for any language designer, including computer languages. Ithkuil: A Philosophical Design for a Hypothetical Language http://www.ithkuil.net/00_intro.html
    2 points
  2. Typically we just use the context help. If you enter a description for a control/indicator, that will show up in the context help window. You can programmatically show/hide that. So you just have a help button that pops it up. Then when they hover over a control/indicator the description shows up in the context help window.
    2 points
  3. No. LabVIEW will have four viewing sizes and will automatically switch between them every quarter hour, which we feel should give you time to focus on the broad overview (on the hour), the major architecture components (15 minutes past), the individual functions (half past) and the algorithm details (15 minutes before) in good rotation in order to keep your overall application fresh in your mind. The front panel will scale inversely, so that both panel and diagram will be at the same scale at half past the hour. In all honesty... we are years away from even thinking about UI gestures for this. Keyboards may be obsolete by the time it is done. Years. No, I'm not joking, exaggerating, making stuff up or trying to set false expectations.
    2 points
  4. After two years "leeching" content every now and then from the Lava community I think it's time to contribute a little bit. Right now, I'm working on a project that involves lots of data mining operations through a neurofuzzy controller to predict future values from some inputs. For this reason, the code needs to be as optimized as possible. With that idea in mind I've tried to implement the same controller using both a Formula Node structure and Standard 1D Array Operators inside an inlined SubVI. Well... the results have been impressive for me. I've thought the SubVI with the Formula Node would perform a little bit better than the other one with standard array operators. In fact, it was quite the opposite. The inlined SubVI was consistently around 26% faster. Inlined Std SubVI Formula Node SubVI evalSugenoFnode.vi evalSugenoInline.vi perfComp.vi PerfCompProject.zip
    1 point
  5. You should probably check the inheritance properties for your class. /J
    1 point
  6. Here's the example code for setting the CCSymbols programmatically. CCExample.zip
    1 point
×
×
  • Create New...

Important Information

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