Jump to content

drjdpowell

Members
  • Content Count

    1,690
  • Joined

  • Last visited

  • Days Won

    123

drjdpowell last won the day on July 1

drjdpowell had the most liked content!

Community Reputation

434

7 Followers

About drjdpowell

  • Rank
    <customize this text>

Profile Information

  • Gender
    Male
  • Location
    Oxford, UK

LabVIEW Information

  • Version
    LabVIEW 2017
  • Since
    1999

Contact Methods

Recent Profile Visitors

8,579 profile views
  1. Seems reasonable; added issue. https://bitbucket.org/drjdpowell/sqlite-labview/issues/6/add-a-execute-sql-1d-cluster-results Unfortunately, I've just released a new version, but it will go into next version.
  2. In an attempt to standardize my handling of formatting timestamps as text, I have added functions to "JDP Science Common Utilities" (a VI support package, on the Tools Network). This is used by SQLite Library (version just released) and JSONtext (next release), but they can also be used by themselves (LabVIEW 2013+). Follows RFC3339, and supports local-time offsets.
  3. Have a look at the latest version 1.11 release. It adds a "Parameters" input to "Execute", which accepts a cluster of parameters to Bind. The tool you want would use similar Variant techniques. Note, however, that using Variants adds possibly not-insignificant overhead to each row returned, as compared to getting a cluster using the lower-level API, so I would not recommend it where performance really matters.
  4. Do you not want to prepare a statement and build your clusters in a loop? Eventually, a VIM could do this in a single VI, but the library is currently in LabVIEW 2013 so no VIMs.
  5. I'm having trouble with VIPM 2020 (the one with the major redesign) . The problem is the main VIPM window doesn't show up on my Windows 7 virtual machine. I would like to downgrade to VIPM 2019, but I cannot find the installer for that anywhere.
  6. Interesting quote from the ex-NI person posting on Reddit:
  7. I've pointed out the sluggishness. It's actually the slowness of opening front panels and block diagrams and in opening right-click menus that is a bigger problem, IMO.
  8. That's more of a Source-Code-Control issue than multiple LabVIEW projects using common code. I have clients where there are multiple projects using common code, but all code is under a single repo. I'm not sure yet about NXG changes here. I have basically two types of reuse. VIPM packages developed usually on an earlier LabVIEW version and used across many projects at many customers (with the main ones being on the Tools Network), and customer common code shared by different sub-projects for a single customer.
  9. So... did anyone have a 1-on-1 interview with NI? I've spent some time with NXG over the last week and made multiple comments, though in a private NI forum so I can be completely honest. Can't tell if anyone from NI has read these comments.
  10. Tone of voice doesn't come through on the internet, X__. You need to be more clear or start using emojis 🙂 AQ, I'm thinking about the Project changes, as I had not appreciated how significant the change is.
  11. I think you need to give the User a choice at step 2 of what to do with the loose files. In my case they are just deprecated VIs that never got deleted (deleting files in Current Gen is very inconvenient). Step 3 need a choice too, as adding the shared files to one of the projects will usually be the right choice.
  12. JSONtext was a single project, but for some reason the conversion tool created two projects: "JSONtext" and "LooseFiles_JSONtext for NXG", plus a "Shared" folder, which actually held the JSONtext.gcomp. I fixd the issue by: closing NXG moving the floder with all the JSONtext files into the same "JSONtext" folder as teh JSONtext project reopening the JSONtext project "Excluding" (bad terminology?) the now-broken JSONtext.gcomp "link" (was annoyed there was no way to fix the link by pointing to the new location) "Add file.." to add JSONtext.gcomp from new location (was pleasently surprised that this then fixed all dependencies without LabVIEW CGs endless dialogs)
  13. So where is a good forum for discussing NXG? Here on LAVA? I'm not one who likes short 1 on 1 private talks nor am I in to "workflows". But I could make lots of feedback on NXG if I have time to craft posts. Right now, for example, I'm trying to make sense of the NXG Project created by the conversion tool from my JSONtext library. I'm completely stuck at not knowing what a "Link" is, and how I can get the JSONtext.gcomp to not be a Link. As a "link", namespaces don't seem to work (I can create a namespace, but not add anything to it) and I suspect this is because a "link" is some kind of leser membership in my project. Maybe. Who knows. I cannot find anything in the NXG help on what a "Link" is, or how to open up the JSONtext.gcomp as not a link. In general, I'm experiencing a lot of "blank stare" moments in trying to figure out this software. Can it really be designed for new users and non-programmers?
×
×
  • Create New...

Important Information

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