Jump to content

bjustice

Members
  • Posts

    94
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by bjustice

  1. For what it's worth, the INI file and INI file signing isn't that big of a pain. Somewhere in the links posted previously is an INI signing tool. NI basically open-sourced this. Do it once, and never worry about it again.
  2. There is also a presentation on youtube, which I found helpful: https://www.youtube.com/watch?v=xXGro_DylHs&ab_channel=LabVIEWArchitectsForum FWIW, a few lessons learned: The project provider VIs have to be installed in the LabVIEW resource folder. Distributing this through VIPM makes this super easy to specify this install location, and also turn on "require LabVIEW to restart" after install You have to restart LabVIEW to test code changes The code executes in a separate LabVIEW context. This can cause some weird behavior, I found that not all code runs in this context safely
  3. Was there ever a call for presentations for this event? Or should we expect for this to be all NI presentations? Will there be a LAVA (advanced users) track?
  4. yikes, what a weird bug. good to know, we're about to upgrade
  5. I've used the G Web Development Module (fairly heavily) once for a project. Also used the MediaMongrels WebSocket API to then have the WebVIs talk back to a LabVIEW application. Worked out quite well. The most alarming aspect of the G Web Development module seemed to be the lack of a user-base. I struggled to find any examples online excluding NI's own examples. The darkside forum felt like a ghost town when I asked for help with a problem. Even now, looking online, I don't see any published roadmap or planned features for the G Web Development. It's kinda sad. I really liked working with what existed.
  6. It was a pleasure having you on the team Shameless plug, we are still hiring:
  7. For what it's worth, I've been heavily using/stress-testing that padding code for flattened strings in TDMS. On the Windows OS, I've had no issues. I'm sad to hear about the issues on the Linux RT OS. I think the saving grace is that, I rarely ever need to read a TDMS on a Linux RT. Usually it's create/write to TDMS on RT, then read on Windows
  8. I just go to see all of you guys "dance" at the Spazmatics band night
  9. @Porter @Antoine Chalons There's some background info here. A few things. Both of those libraries are branches of the Erdos Miller code. However, I communicated all of my modifications to Antoine, who then re-implemented them in his library. I have little intention of making additional changes to my branch. Conversely, I suspect that Antoine intends to continue to support his branch, if only in a limited manner. BlueTOMLSerializer is not just a TOML library. It was written as a TOML-based plugin for the BlueSerialization engine. https://www.vipm.io/package/blue_origin_lib_blueserialization/ This is a large piece of code that handles serialization and deserialization of classes quite well. The user can select an implementation of JSON, TOML, or other by choosing a different plugin library. I fully intend to modify BlueTOMLSerializer to drop all the TOML code and directly consume Antoine's library as a dependency. This, for example, is what I do for JSONtext. Unfortunately, I'm waiting on a specific feature request to be implemented in Antoine's library: https://github.com/AntoineChalons/lv-toml/issues/24 Hope this helps
  10. My goal is always to produce a user interfaces that users won't recognize as being written in LabVIEW unless you told them. 2 examples of this that I've seen online come to mind: VIPM (VI Package Manager. This received a major UI overhaul in 2020.) Scout TDMS viewer (From Signal.X)
  11. Today I learned. Thanks Logman
  12. lockup.vi I ran into a strange LabVIEW (bug?) today. (Note, I'm using LabVIEW 2020 SP1) Figured it was worth sharing, maybe you guys have insight here. I've attached a VI that demonstrates the behavior. Basically, if you click the "Do" button, then LabVIEW will completely lockup. You have to hit the abort button or task kill to escape the lockup. In the "False" case below, the event structure loop doesn't get kicked off. However, it seems like LabVIEW locks up when the Do button is pressed... perhaps indicating that LabVIEW is waiting for the event structure to fire off the event... which, of course, never happens in the False case. What's even stranger is that if you flip the disabled structure, you'll see that the code doesn't lockup if the case structure is given a constant False input. This tells me that compiler shenanigans are at play. Weird weird weird
  13. I ended up copying VIPM verbatim: Use /\ and \/ Make the active column BOLD I agree that overlaid buttons are better and feasible, but would take alot of work to get correct with things like column resizing. The VIPM solution is low effort, robust, and not thaaat bad looking.
  14. Argh, you're right, there is a limitation. It looks text properties (size, color, style, fontname) are global for each individual cell. i.e. I can't have a cell with both Segoe UI font and then also some text using Symbol font in the same cell. This means if I put Symbol arrows in a header cell, then I can't place descriptive text next to the arrow.
  15. Oh, really? Ok, I'll give this a try and report back any issues. If it doesn't work, I'll just go with your /\ idea, I didn't think of that
  16. OOooo, I think I might have a solution. The font package "Symbols" has a bunch of symbols and arrows in it: This font package ships with Win 10, which is the only OS this product needs to run on right now, so that should work
  17. In many modern non-LabVIEW UIs, tables can be sorted by clicking on the header. There is then usually a glyph to communicate this feature. Non-LabVIEW example: I'm trying to reproduce this behavior in LabVIEW, but I keep hitting roadblocks. Notably: LabVIEW doesn't allow for symbols in table headers LabVIEW ascii table doesn't have any up or down arrows. There is an up carrot ^, but not a down carrot. I'd love to know if anyone has any suggestions or workarounds.
  18. @jdpowell @LogMAN @Antoine Chalons @Aristos Queue I recommend that you guys take a peak at this code. We're not normally able to release code like this to the community, but I managed to collect approval for this particular library on grounds that it was very low level and very intertwined with other open-source community code. (literally recursively entwined with JSONtext lol.) A few notes: ___ This library leverages the new "LVClass Serializer" input to JSONtext: Soo, thanks at JDP for adding this input. Very helpful. __ Antoine, the TOML serializer here is not yet directly consuming your LV-TOML library. I would realllly love to make this happen though. In order to consume LV-TOML, we'll need to add a "LVClass Serializer" input to LV-TOML in exactly the same manner as JDP added this to JSONtext. For the moment, the TOML code in this library is a branch of the old Erdos Miller TOML library... except that I've added the code required to hook into class deserialization stuff. __ Logman, I took a look at your recently published "JSONtext Object Serialization" library https://www.vipm.io/package/pnr_lib_jsontext_object_serialization/ Very cool code! Your LabVIEW composition library has been quite useful. In fact, it's a dependency to this library! So, a big different between your library and this Blue library is that we chose not to use composition for serializing/deserializing classes. We had a few reasons for this, and it's actually described in more detail on the repo readme. However, this Blue library ships with a very nifty "BlueVariantView" package. This exports any LabVIEW data structure to a colorized tree control. (I was inspired by the LAVA VariantProbe library, so I made my own... but better.) I used your composition library within this tool to decompose maps, sets, and classes. Take a look, super cool! __ Lastly, Aristos, I'll just cryptically say that your an inspiration, and I hope this code benefits you
  19. LAVA friends, Do you like JSONtext? Do you like LV-TOML? But do you always wish that either of these libraries supported LabVIEW classes? Well, with this library, now they do! The more in-depth documentation can be found at the official source code repo: https://github.com/justiceb/BlueSerialization The VIP packages can either be downloaded here, or directly from VIPM. On a related note, if you like the code, consider checking out the following link:
  20. Version 1.0.0

    8 downloads

    Serialize and deserialize LabVIEW classes using either JSONtext or TOML Official documentation: https://github.com/justiceb/BlueSerialization
  21. View File BlueSerialization Serialize and deserialize LabVIEW classes using either JSONtext or TOML Official documentation: https://github.com/justiceb/BlueSerialization Submitter bjustice Submitted 08/05/2021 Category General LabVIEW Version 2018 License Type BSD (Most common)  
  22. I don't understand this website. They are pushing this whole "chat with other attendees", but there are no chatrooms? You have to search for someone by name?
×
×
  • Create New...

Important Information

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