Jump to content

X___

Members
  • Posts

    355
  • Joined

  • Last visited

  • Days Won

    25

X___ last won the day on March 3

X___ had the most liked content!

2 Followers

Profile Information

  • Gender
    Not Telling

LabVIEW Information

  • Version
    LabVIEW 2021
  • Since
    1995

Recent Profile Visitors

4,768 profile views

X___'s Achievements

Collaborator

Collaborator (7/14)

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

Recent Badges

81

Reputation

  1. There is NO public bug tracker in LabVIEW... In fact, I am not even sure there is beta program anymore...
  2. A bit like Egyptian hieroglyphs.
  3. For NI's defense, this is probably only visible on 1080p displays. It speaks volume about the state of LabVIEW when this becomes a new feature worth discussion on LAVA...
  4. OK, my bad. I think I know what you are referring to: I am not sure what this means though, as I see no effect of the default font style on terminal, bundle, etc. sizes, only on the labels (in LV 2021 SP1).
  5. Care to expand? Don't see anything in the changelog (sorry, there is no changelog).
  6. https://seekingalpha.com/news/3949487-national-instruments-sale-process-likely-to-be-completed-in-early-april-report
  7. I am looking forward to reading "Undo doesn't work anymore" in 2024Q3 and "colors are all gone" in 2027Q5... 🍿🍹
  8. X___

    U32 or SGL?

    Almost got me. I was certain it was blue.
  9. X___

    U32 or SGL?

    For info, this showed up in a VIM, in which I was playing back and forth between the representation of the input data to check different cases. I guess it throws off the IDE context help... and maybe more.
  10. X___

    U32 or SGL?

    No comments and couldn't care less whether it is fixed or not.
  11. https://www.fool.com/investing/2023/03/10/who-will-win-the-bidding-war-for-national-instrume/
  12. https://finance.yahoo.com/news/ni-acquires-set-gmbh-accelerate-140000459.html
  13. I am not the one confused by this post, but I have to wonder: with a 17 MB BD and a code complexity of 18.1, maybe considering breaking stuff into subVIs and refactoring is in order? In my case, this tool was helpful in setting priorities: https://www.abcdef.biz/pi_free.htm
  14. I only meant that 2023 Q1 is the first version to officially support Windows 11 and that apparently, the head count in the LabVIEW R&D team is either classified or not to be admitted in public.
  15. There is no need for gut feeling: the simple fact that they are not even trying to hype the future of LabVIEW is speaking volume. We implicitly learn that the LabVIEW team has been gutted or at least not given the means it needs to even keep in sync with OSes (https://www.ni.com/en-us/support/documentation/supplemental/22/ni-product-compatibility-for-microsoft-windows-11-.html). Heck, TestStand and VeriStand themselves, of which I know nothing but understand are where NI is investing its resources, are not Windows 11 ready. As for the rest, I guess you can check the release notes for 2023 Q1 (https://www.ni.com/pdf/manuals/labview-2023-q1-and-drivers.html#examples) to understand that the T's are not even crossed anymore, since the examples for this version are apparently to be found in the \LabVIEW 2022\examples directory... I am not sure it is fun to work at SpaceX, but I doubt there is much feeling of exhilaration at LabVIEW R&D nowadays...
×
×
  • Create New...

Important Information

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