Jump to content

Michael Aivaliotis

Administrators
  • Posts

    6,196
  • Joined

  • Last visited

  • Days Won

    103

Posts posted by Michael Aivaliotis

  1. One thing that I was pleasantly surprised by, in the video presentation. Was the announcement of a 6-year partnership (not sure what that means) with the FIRST robotics organization to provide hardware like the roboRIO. I was almost certain that NI abandoned this effort years ago. It's nice to see them reaffirming this relationship. Proof is in the actions, so we'll see. I hope this means more active support to the teams in regards to promoting LabVIEW and not just, ya we will keep selling roboRIO.

  2. 16 hours ago, JKSH said:

    There's an Idea Exchange entry about this for LabVIEW CG, but it really should extend to NXG too: https://forums.ni.com/t5/NI-Package-Management-Idea/Install-the-same-package-to-multiple-versions-of-LabVIEW/idi-p/3965419

    Well it kinda does apply to both considering NIPM should manage both CG and NXG. I've heard through a reliable source that NI is seriously intent in solving this problem in NIPM for both CG and NXG.

  3. 12 hours ago, gregoryj said:

    Ok great. My router is far away from my desk, so I'd like to use wifi after the initial set up. Just ordered the raspberry pi and excited to play around with it!

    Well, you could plug your computer directly into the raspi port, no router needed. Or purchase a cheap usb to ethernet dongle and add an extra port to your PC. This is what I do for my cRIO work.

    https://www.amazon.com/dp/B00M77HMU0/ref=cm_sw_r_tw_dp_U_x_AJJUEb7TVD7CS

  4. My understanding is that Maps are the same as variant attributes. Except with maps, obviously you don't have the overhead of VariantToData or DataToVariant, when inserting data or looking up data. That can be a huge overhead in some cases. Plus you need support code to prevent variant conversion errors when using the wrong typecast.

    Variant attributes are slightly more powerful than Maps because you can insert any type. However, one could argue that this is a characteristic that leads to messy designs. The same variant wire could contain mixed values types within it. Each with its' own type conversion VIs. I think if you've been using variant attributes and it works for you, I don't think you need to rewrite everything. But they definitely need to be considered in new designs. Because you don't have the overhead of creating all the glue VIs for the data conversion, they are frictionless to use and start using out of the box.

  5. 5 hours ago, Neil Pate said:

    In order to resize an array you have to click on the tiny dot in the middle of the drag handle that only appears if your mouse is leaving the control and is some weird distance way from the border.

    image.png.3acd23adcd071aa733ab678af1d3b1e5.png

    In other words, in this picture in order to get the resize drag handle to appear I have to move my mouse over the control, then out a little bit into the middle of space with no visual indication how far out to move it until the horizontal bar appears and then find the tiny dot in the middle and then drag that. 🤮

    How could this UX make it through 8 years of development?

    2020-05-07 22-49-46.mkv 3.22 MB · 3 downloads

    i watched the video. Yikes, ya, that's pure garbage.

×
×
  • Create New...

Important Information

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