Jump to content

MikaelH

Members
  • Content Count

    812
  • Joined

  • Last visited

  • Days Won

    44

MikaelH last won the day on May 21

MikaelH had the most liked content!

Community Reputation

181

3 Followers

About MikaelH

  • Rank
    The 500 club
  • Birthday 12/25/1972

Profile Information

  • Gender
    Male
  • Location
    Sydney

LabVIEW Information

  • Version
    LabVIEW 2016
  • Since
    1996

Contact Methods

Recent Profile Visitors

9,957 profile views
  1. You can fix it in 2 ways. 1. Force open the VI and change the dll call (LabVIEW.exe) to not run in the user interface thread. I've tested this and this will speed it up 1000 times or so but... this could crash LV if this code is running in any of LV's special Application instances like Project Provider App instance (And that is where I need the performance improvements in the OpenGDS UML Modeller). 2. Yes, use a Map or Variant look up. See example VI GetTextRect_AnyThread.vi
  2. Looks Cool Maybe we should make a public framework for this and a big open source library of UI components. FYI you don't need to wire an empty class constant to the create methods 🙂
  3. Many controls have invoke nodes like this to convert the click position to more meaning full info, e.g. where in the X/Y plot you click.
  4. I've not dared to outsource the building to a build server yet, mostly because we get these strange build errors from time to time, like "This VI broke during the build". Also since my team does quite many builds and we would need multiple build servers since a build could take an hour, and sometime I need to build 6 version right away and that could lock up the build server for 6 hours. But if you get it working close to 100% let me know, then we might switch over.
  5. If you switch the disabled structures, it shows you how it works better. Using the Graph.Plot feature is just an option, I would probably use a separate Picture conttrol to the left of the Graph that hold the titles. Or when we want to have nice/different types of plot we use a WebBrowser container with html/javascrip code.
  6. So 2014 should be good then 🙂 Maybe it's time to think about upgrading 😉 2020SP1 is Awesome, especially now with Interface support 🙂 Horisontal BarChart-2014.vi
  7. Is 2016 okay? Horisontal BarChart-2016.vi
  8. You can do something like this: Horisontal BarChart.vi
  9. Thanks, I missed that. Strange that is allows any text and messes up the JSON content completely if it's not valid json.
  10. Hi, I do like the new “Retain All Errors” in the Merge Errors, it coverts the Error source to an JOSN array of errors. With that change NI added some extra JSON Error VIs like the Write attribute. But I can’t get those VIs working? I couldn’t find anyone else complaining about this, sure I can just fix the issue myself since the VIs aren’t locked. Are anyone using these VIs?
  11. You can do this. I thought that was the main reason for adding interfaces ☺️. BTW, if you're using LV2020 and classes, the new OpenGDS beta version makes it easy to work with interfaces 🙂
  12. We modify code while LV is running all the time 🙂 We even have a Quick Drop shortcut that toggles a Sub-VI's Loading Option between "Load with callers" and "Reload for each call".
  13. Hi, I just posted my GOOP Training course material here: https://forums.ni.com/t5/GDS-Goop-Development-Suite/GOOP-Course-Material/td-p/4101113
  14. Same here. It locked the whole OS for some reason when I start NXG.
×
×
  • Create New...

Important Information

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