Jump to content

drjdpowell

Members
  • Posts

    1,964
  • Joined

  • Last visited

  • Days Won

    171

drjdpowell last won the day on February 28

drjdpowell had the most liked content!

Profile Information

  • Gender
    Male
  • Location
    Oxford, UK

LabVIEW Information

  • Version
    LabVIEW 2017
  • Since
    1999

Recent Profile Visitors

16,688 profile views

drjdpowell's Achievements

  1. Yes, at some point I intend to make an interface that has "to JSON" and "from JSON" methods, that one can inherit from. But at the moment JSONtext is based in LabVIEW 2017.
  2. I will fix the inconsistance, either by making comlex numbers full not supported or fully supported.
  3. Not necessarily, but it is trickier than it looks because of those "multipoint paths" that unflatten does not support. A path like $.a.[new,old].b[4].c.d, for example. If all paths were straightforward like $.a.b.c.d then it would be easy. Although I use JSON for configuration, I'm not using it in the same way you are doing, so it hasn't motivated me to solve this issue. Sorry.
  4. See if "Unflatten JSONpath Array to Object" will do what you want. It will create the extra levels if needed.
  5. That vipm package seems to have gotten corrupted somehow. I'll contact NI about it. In the meantime, try getting it from here: https://forums.ni.com/t5/JDP-Science-Tools/Out-of-Memory-Error/m-p/4335019/highlight/true#M156
  6. Unable to install to LabVIEW 2023 (64-bit) or LabVIEW 2019 (64-bit) as VIPM doesn't think it is supported in LabVIEW 2023, not sure if this is true, or an oversight somewhere. It looks like people are actively commenting on it this year, so I just wonder if its my system specific. I did try downloading from NI, LAVA and VIPM.

    1. drjdpowell

      drjdpowell

      I think there might be a corruption of the vipm file.  I can't get the download to work even though the original I have installs fine.

    2. drjdpowell
  7. Can you try forking the repo? Then making a pull request? I only have a free Bitbucket account and there is a limit on how many people I can add to my repos.
  8. Compiled object cache is an SQLite database, I believe, so is suspect you can easily delete VIs from it. Though you'd have to test that.
  9. I'm afraid I don't have an example. I did once prototype a version where I swapped out the flattened message format for one that used JSON (I recommend JSON as an easy, reliable format to go between languages).
  10. I use the "Advanced PNG Export" feature of https://pictogrammers.com/library/mdi/. This allows some customisation of icon (size, colour, transparency, border) before downloading.
  11. Why are you making Setting modules at all, rather than just having the other modules just read the INI file directly? This seems very over complicated.
  12. Quite a lot of good architectures are based on using messages between semi-independent modules, with the modules being based on a standardized template. There are a few such "frameworks" publicly available via vipm.io that you could look at. Mine is "Messenger Library", which has some instructional videos.
  13. I've long thought the Event API has bad naming. If the Event Reg Refnum was called "Event Queue" and the User Event was called "Event Generator", then it would be easier for people to understand it.
×
×
  • Create New...

Important Information

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