Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Darren last won the day on January 22

Darren had the most liked content!


About Darren

Profile Information

  • Gender
  • Location
    Austin, TX

Contact Methods

LabVIEW Information

  • Version
    LabVIEW 2020
  • Since

Recent Profile Visitors

7,416 profile views

Darren's Achievements

  1. The multiple patterns nugget was broken in LabVIEW 2023 Q1, but it works in LabVIEW 2023 Q3 and later.
  2. The App Builder API is not supported within a built EXE. It can only run in the LabVIEW editor. More generally, there is no way to build a LabVIEW EXE that can build LabVIEW EXEs.
  3. There is an App Builder API which will allow you to accomplish this task, but it is not officially supported by NI. The VIs are in [LabVIEW 20xx]\vi.lib\AppBuilder\AB_API, and there is an examples subfolder there with a few examples that should help you get started.
  4. There have been a couple of patches released for LV 2023 Q3 that you can install from NIPM that fix (among other things) some App Builder issues. If y'all install those patches and still see issues, I know that LV 2024 Q1 is releasing shortly, which also includes some App Builder fixes. Additionally, if y'all are able to share code, feel free to PM me and I can get Bugs filed to R&D for build issues that we can reproduce in-house.
  5. If your cluster contains elements that are all the same data type, you can use the Cluster To Array function. If your cluster contains elements that are different data types, then the approach you describe won't really work due to LabVIEW's strict data typing.
  6. What is your use case for needing this behavior?
  7. I believe this has been reported to LV R&D as Bug 2561077. It is scheduled to be fixed in the LabVIEW 2024 Q1 release, and they are also researching whether or not to include the fix in a patch to LabVIEW 2023 Q3.
  8. If you're still having issues, and you're able to share the VI with me, let me know... I can take a look.
  9. (Disclaimer: I am not an NI insider, and I have no inside knowledge of the pending Emerson acquisition) I think we're all sort of in a holding pattern waiting to see how the Emerson acquisition plays out. Emerson's outward messaging seems very positive towards LabVIEW, which I find encouraging.
  10. I like remixicon.com. Everything there is free for personal or commercial use. Here's what they have for a search term of "door":
  11. Antoine is correct, those diagrams should function identically.
  12. The issue was reported to LV R&D as Bug 2317159. It was introduced in LabVIEW 2022 Q3 and fixed in LabVIEW 2023 Q3. The Error 13 occurs when the LabVIEW Class private data includes certain types of .NET references, or a reference to a .chm help file. More details: LabVIEW 2022 Q3 included a "fix" to how linkages to .NET assemblies are adjusted in a build output. Unfortunately this "fix" caused the issue you're seeing. LabVIEW 2023 Q3 uses a new mechanism for app builder caching under the hood, which removed the codepath that was causing the Error 13 altogether.
  13. I think this issue may have been fixed in LabVIEW 2023 Q3. Are you able to upgrade and try it out?
  14. Again, it all comes down to what framework(s) "click" for you. I personally would develop the application entirely with DQMH, here's a very introductory article on how DQMH and HAL concepts work together. Other developers would have great success sticking purely to Actor Framework. Still others with JKI SMO. Learn about the different frameworks, see which one(s) align the best with your mental model, and go in that direction. But whatever you do, don't create a new framework. P.S. - I wrote this article which might also be a good resource for you.
  15. I worked on a project a while back that used JKI SMO for some lower-level functionality and had DQMH modules up top that used the JKI SMO classes. It's definitely possible, and desirable for some teams, depending on the skill level of the team members, their preferred frameworks, and which parts of the application they're responsible for.
  • Create New...

Important Information

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