Jump to content

bjustice

Members
  • Posts

    79
  • Joined

  • Last visited

  • Days Won

    4

bjustice last won the day on August 31

bjustice had the most liked content!

About bjustice

  • 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,509 profile views

bjustice's Achievements

Rookie

Rookie (2/14)

  • Conversation Starter Rare
  • Dedicated Rare
  • First Post Rare
  • Collaborator Rare
  • Reacting Well Rare

Recent Badges

20

Reputation

  1. Today I learned. Thanks Logman
  2. 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
  3. 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.
  4. 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.
  5. 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
  6. 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
  7. 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.
  8. @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
  9. 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:
  10. Version 1.0.0

    7 downloads

    Serialize and deserialize LabVIEW classes using either JSONtext or TOML Official documentation: https://github.com/justiceb/BlueSerialization
  11. 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)  
  12. 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?
  13. My understanding is that the functional safety editor, paired with the yellow c-series safety modules yield a SIL-3 (safety integrity level) certified hardware/software solution. This SIL level is often a requirement for situations that could put humans at risk of harm. Neither the LabVIEW nor NXG environments would be able to carry this rating, so they stripped out a slim version of NXG and pushed it through a bunch of verification to obtain the safety rating. I played around with it, and it was pretty neat. I wouldn't regard it as anything more than a smart/configurable relay capable of fitting into a c-series slot and sending data back to the controller via the backplane.
  14. The Voyager probes are truly amazing. The "Pale Blue Dot", captured by Voyager 1, is perhaps the coolest picture ever taken. Some cool facts on this from NASA: https://solarsystem.nasa.gov/news/1175/10-things-you-might-not-know-about-voyagers-famous-pale-blue-dot-photo/
×
×
  • Create New...

Important Information

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