Jump to content

bjustice

Members
  • Content Count

    64
  • Joined

  • Last visited

  • Days Won

    2

bjustice last won the day on April 6

bjustice had the most liked content!

Community Reputation

14

About bjustice

  • Rank
    Very Active
  • Birthday 10/31/1990

Profile Information

  • Gender
    Male
  • Location
    Van Horn, Texas
  • Interests
    Rockets

LabVIEW Information

  • Version
    LabVIEW 2017
  • Since
    2012

Contact Methods

Recent Profile Visitors

1,254 profile views
  1. Correct. Ahh, I typically only read the files. But yeah, the writer portion of the code doesn't in-place edit a file, so yeah, the comments would be lost. Good point. I'm not sure of the way around this. How is JDP handling this? I assume that he's going to have the same issue with JSONtext (since he added comments in the latest JSONtext release)
  2. I've found that comments in the original LV-TOML library seem to work pretty well. That issue ticket that you linked has been the only bug related to comments that I've found
  3. Does anyone know if it's possible to compose/decompose map/sets in LabVIEW? @LogMAN wrote a fantastic "LabVIEW Composition" library which is able to : compose/decompose LabVIEW classes decompose maps decompose sets However, there is no support for composition of maps/sets. (Link: https://github.com/LogMANOriginal/LabVIEW-Composition) @jdpowell and @Antoine Chalons had an interesting discussion on a JSONtext issue ticket about this subject: (link: https://bitbucket.org/drjdpowell/jsontext/issues/74/add-support-for-maps-set) However, it does
  4. in "TOML to LabVIEW.vi" Here are the mods that I made. Those cyan VIs are from the JDP utility VIPM package that ships with JSONtext
  5. Now is the time to do it, TOML just released a v1.0 spec. I, for one, would buy you a beer at NI week
  6. Yep! TOML is like INI file syntax learning how to do everything that JSON can do... with comments. I'm a fan. I've also been using the Erdosmiller library. I've found a few bugs, it's not full-feature, and it's not TOML 1.0 compliant. (TOML just 1.0'd recently). It's the best I've found thus far though, and it's been working well enough for me.
  7. Correct, they don't sell licenses anymore. Just trying to be helpful and provide another datapoint. I'm in the same boat at the moment - looking for a good Python/LabVIEW integration solution, but there doesn't seem to be anything that has been able to eclipse the capabilities of the Enthought toolkit.
  8. I've been a big advocate for the Enthought Python integration toolkit in the past. Unfortunately, the product was discontinued when LabVIEW introduced the native python node. I'm still scraping by on this product as I've not found a good alternative, and the built-in LabVIEW python node doesn't meet my needs. Under the hood, the Enthought product was just a TCP link to Enthought's flavor of python called Canopy... which has also been discontinued. This product was fantastic for a few reasons: Canopy environment could be packaged into a lightweight Python runtime engine, which
  9. Ahh, I did not realize that they were located there. Thanks!
  10. Thanks, great thread! Does anyone know how I might be able to get ahold of, or export all of these cool symbols as BMP files? It looks like all of the extended symbols in the special MCL are stored as "built-in symbols" for the MCL. As such, I can't seem to export them using the method: Custom Item Symbols:Get Symbol. (This method returns an empty data array.)
  11. I feel the need to highlight the absurdity of how Shaun answered this question within 4 hours... about a post that he made 10 years ago. This community is amazing
  12. Upvote Scratch. I used to teach scratch to 12 year old kids at summer robotics camp. Very approachable, fun to make games. Lego Mindstorm is another good one
  13. Riiight, so Hooovahh is hitting the nail on the head here with my thoughts exactly. It would have been nice to maybe make the plugin menu a bit more intelligent such that it wouldn't have these "create constant, create indicator, create control" for these situations. The consistency argument is interesting and not something that I had considered. Give me 2 months with this new change, and I'll report back on how my muscle memory and opinion has changed. I might indeed be the old man yelling at a cloud right now. I'm trying to beat Darren for fastest programmer in the wo
  14. I've started working in LabVIEW 2019 SP1, and I've observed that the right-click menu on the block diagram has changed such that "create constant/control/indicator" are always at the top for almost every block diagram action. Example: If I recall, this was a pretty popular right-click menu plugin that alot of LAVA folks were using in prior versions of LabVIEW. It looks like NI simply cemented the idea in base LabVIEW 2019. I'm just curious though, does anyone here find this annoying? It's really wreaking havoc on my muscle memory. Furthermore, in situations such as
×
×
  • Create New...

Important Information

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