Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 10/29/2020 in all areas

  1. I believe this now referred to as "Agile" 😉 But in all seriousness, not attempting something for fear of failure is not something I have ever really worried about. Also, it is pretty much impossible to fail on 100% hobby/pet-project/learning experience.
    2 points
  2. 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".
    2 points
  3. Just as an extra reference point, this post contains a redone winutil.llb file where all the references to the private winutil DLL have been removed and as far as possible replaced to compatible direct calls to the according Windows APIs. In addition the Call Library Nodes have been updated to be compatible for 32-bit and 64-bit operation and I also added one or two functions from this example into the library as well. In order to support seamless 32-bit/64-bit support one has to make sure to use the new Windows control contained in that lib for everything and modify any other Call Library Nod
    2 points
  4. “There was this fence where we pressed our faces and felt the wind turn warm and held to the fence and forgot who we were or where we came from but dreamed of who we might be and where we might go...” -- Opening lines of “R is for Rocket” by Ray Bradbury I spent 20 years building this G language of ours. It’s time for me to go enjoy the fruits of that labor as a user! I will still be employed by NI, but I will be working full time for Blue Origin. As part of the NI “Engineer in Residence” program, I will be on loan to Blue Origin to revise their engine and support test systems. They
    1 point
  5. There is something strange about how this library is managed. For some reason it seems to work if the VI is part of a project, but not as a standalone VI. Standalone As part of a project I did not reproduce the entire example, so it might fail. At least you can try adding your VI to a project and see if it works (make sure the assembly is listed under Dependencies).
    1 point
  6. I have invented Y Controls and I am trying to create a VI Package for installing them. I would like it to result in "Y Control" being an option when selecting File -> New from the LabVIEW menu. But my .vipb file doesn't seem to do anything; no output, no errors, just a big NOP. Any help would be appreciated. Y Controls.zip
    1 point
  7. I just added an explanation of how to add to the New dialog on the LabVIEW Wiki: https://labviewwiki.org/wiki/New_dialog If you have any ideas to help me make QControls better, let me know. I have a thread on the QControl Enthusiasts page: https://forums.ni.com/t5/QControl-Enthusiasts/QControl-Usability-Improvements/td-p/4101397?profile.language=en
    1 point
  8. Uhuh. Seat-of-your pants design; the fastest way to project failure.
    1 point
  9. 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
    1 point
  10. As a publisher of packages myself, I really like the interface and how easy it is to have a package of mine find its way to the Community repository. It was always nice to have the LAVAG code repository (same info, direct ungated access), but having the packages accessible to anyone just by virtue of refreshing the VIPM package list is really a nice feature. @Antoine Chalons, sure I'll move the Controls Addon to VIPM Community... Already put in the request!
    1 point
  11. I've recently released the Variant Repository code as a package on VIPM.IO as VIMs. Some of the magic is lost going from a series of XNodes to VIMs, and even more wind is taken out of my sail by the fact that Sets and Maps can do what VRs did in a more native way. However I have some code I'd like to share that relies on Variant Repositories, so I cleaned it up for a release. And replacing those functions with Sets and Maps would mean my code could only be used by 2019 and newer. In the future when 2019 doesn't seem so new I'll probably remove the VR dependency. Or maybe I'm being lazy I
    1 point
  12. I have made public a document detailing an old internal feature of LabVIEW that will be of great interest to those of you deploying Packed Project Libraries. Until recent conversations with a customer, I never considered that this would have much utility. The problem this solves: First, you build a packed project library (PPL) from source. Then, you write a VI that calls that PPL. It works fine. But now you load the caller VI under a different target in your project. The caller VI breaks because it tries to load the PPL, and the PPL refuses because it isn't built for the new target. Packe
    1 point
  13. I'm not surprised by this, but thank you for weighing in. Maybe when NXG reaches CG parity in 2050.
    1 point
  14. Ok cool, I will pick it up again. 🙂 Stupidly I am now thinking of moving the game logic to python as this will give me a chance to play with the python integration node in LabVIEW (assuming it is not too slow) and also polish up my python. The intention is that I can modify it while the game is running.
    1 point
  15. @kosist90 Here is a beta version, that you can test if you like: drjdpowell_lib_sqlite_labview-1.12.0.89.vip It's not implemented exactly the same way as your example, but it should work in the same places. See the example "SQLite Parameters in Execute".
    1 point
  16. Actually, we have implemented it in the following way - I attach snippet, and VI itself. VI is broken, b/c it is not part of the library... And the issue is that we are kind of able to use this solution, but then we need to manage somehow the fact, that it should be part of SQLite library. And then, we will not be able to update it from VIPM, b/c we will loose the changes. Could you please suggest, whether such solution could be the part of the original toolkit? If so, my colleague could open pull request, or something... The original VI (which returns just single cluster) was m
    1 point
  17. OK turns out I was looking in the wrong place! You have to browse to just System (Not System.Net.Networkinformation) and there it is.. Also the .net API browser courtesy of Microsoft comes in handy https://docs.microsoft.com/en-gb/dotnet/api/system.net.networkinformation.networkinterface.getisnetworkavailable?view=netframework-4.7.1#System_Net_NetworkInformation_NetworkInterface_GetIsNetworkAvailable
    1 point
  18. Version v1.10.0 (for LV2013+)

    3,103 downloads

    LabVIEW Task Manager v1.10.0 (for LV2013+) This code is Open-Source, and free of charge Authors: Ravi Beniwal, Tim Vargo LAVA Names: Ravi Beniwal, TimVargo Contact Info: Contact via PM at the LAVA site (http://lavag.org) LabVIEW Versions Supported: LV2013 and up LabVIEW Versions Tested on: LV2017 LV2016 LV2013 Dependencies: GPower Error & Warning = 1.2.0.14 lava_lib_tree_control_api >= 1.0.1-1 NI SmartBalloon = 2.0.0.2 OpenG Application Control Library >= 4.1.0.7 OpenG Comparison Library >= 4.0
    1 point
  19. Thanks. Here's a more developed subVI that I've used successfully inside a Pre-build action. I use it to set a Build CC symbol to be equal to the Build Name, so different builds can enable different code. Set CC Symbol.vi
    1 point
  20. enableSecretPopups - I put this token into LabVIEW 2011 for Silver control development, as a quick-and-dirty way to make low-level control edits. I've been giving it out to people on a very limited basis, but I guess since it's out here I'll widen the audience. I show a screenshot of the new menu items in https://decibel.ni.com/content/docs/DOC-17431 Once this token is enabled, you'll be able to see the settings on parts of the Silver controls to get an idea what they do. eg "Left Move" means the part will move left when its "master" part changes size via moving its left edge. "Left Gro
    1 point
  21. Let's see if this image looks better: How it works better... The \00 is the NULL chracter, you have to switch to '\' Coded Display, to get it working. This is the string you can use to tweak the File Dialog bevaviour. *.txt;*.doc;*.html)\00*.txt;*.doc;*.html;\00Image\sfiles\s(*.png;*.jpg)\00*.png;*.jpg\00\00 I'm not sure why it works, and if it always will be supported but it's quite good feature. //Mikael
    1 point
  22. View File JSONtext Package for working with JSON. Uses high-speed text parsing, rather than building an intermediate representation as with prior LabVIEW JSON libraries (this is much faster). Allows easy working with "subitems" in JSON format, or one can convert to/from LabVIEW types. Uses the new "malleable VIs" of LabVIEW 2017 to convert to any LabVIEW type directly. JSON text makes use of a form a JSON Path notation, allowing easy and rapid access to the subitems of interest. Requires LabVIEW 2017 and install by VIPM 2017 or later. Original
    0 points


×
×
  • Create New...

Important Information

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