Jump to content

Val Brown

Members
  • Content Count

    754
  • Joined

  • Last visited

  • Days Won

    2

Val Brown last won the day on May 9 2011

Val Brown had the most liked content!

Community Reputation

25

About Val Brown

  • Rank
    The 500 club

LabVIEW Information

  • Version
    LabVIEW 2018
  • Since
    1998

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. FWIW, this thread so far confirms its original premise, reveals what "the baby" is and what "the bathwater" is.
  2. I've running LV 2015 on W10 since before NI Week and, once I got it set up, it all seems to be working fine. Yair I was able to pin a number of "arbitrary" apps to the Start Panel but it's a bit of an uncertain and occult process: I can't tell what actually worked and what didn't. One thing I did find out was that pinning an app to the Taskbar helped as a first step, but your local results may vary.
  3. There are two things I'd like to say about this thread. 1. It underscores for me how often CLA-level "in-house" projects are undertaken that run more or less in parallel to other such projects. In some ways this is a very good thing as it allows for diversity in approach and implementation but also a robust degree of competition that, hopefully, increases the overall qualitym usability, scalability and extensibility of the various offerings. We have some very brilliant and creative people in this community! But there is also a downside to this diversity and that involves confustion to th
  4. I agree with this. If it compiles -- even it it's "wrong" in what it does -- then it should not "break" in the IDE. Some form of warning that CAN be ignored by those who want to do so, is really the best solution, even if there are lots of LV programmers who routinely ignore errors that are generated by the IDE. In other words, if you really want to setup what some would consider to be a "race condition" then the language should allow for that. No matter how thoroughly the original architecture of the underlying language, there will be "holes" and possibilities that developers will prop
  5. I've built EXEs from code that was migrated -- and updated -- along the way since LV 6i and I've not seen this kind of issue in either 2014 0r 2014.
  6. This is probably a WAY silly idea but did you try setting the working directlory to usr/natinst/LabVIEW-2013/ and then just using labview as the command line (perhaps having done a cd usr/natinst/LabVIEW-2013 first? That might at least generate some other error messages...
  7. It's interesting to believe that 10 or more years old keyboard and mouse based (not even trackpad) UI is going to remain the prevalent benchmark. I strongly suspect that touch interfaces and other gesturing (perhaps some kind of "Leap" process) will supplant physical keyboards and mice like they supplanted punch cards and magnetic tape. MS doesn't have a great track record in developing, let alone inventing, UIs so I also strongly suspect that it will an iOS style user experience that will continue to "lead the way" (as what the US Army Rangers do). It's intuitive -- unless you have year
  8. I thought that was already well known back in the early 80s....
  9. OK, thanks. All info, tips and suggestions welcome....
  10. Still wondering if anyone is using ubuntu to support LabVIEW for Linux?
  11. Val Brown

    Cross post?

    Will this be a new "add-on"?
  12. Outstanding! Great idea and great first guests. as the saying goes: "Break a leg..."
×
×
  • Create New...

Important Information

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