Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 05/12/2021 in Posts

  1. It's only for Linux 64-bit a 64-bit value. And it's seems a bit of a GCC choice, while Microsoft chose to keep long as a 32-bit integer (and not support long long for some time instead insisting in their _int64 private type). And while not sure about the original Sun Solaris versions which might only have existed as 32-bit anyways, the later Linux kernel based versions however almost certainly use the same logic as the other Linux versions, although Sun had a tendency of trying to customize it when they could, and sometimes even when they shouldn't :-).
    1 point
  2. Just a comment, but I have noticed that people very often deal with JSON by looking for the "monster cluster" that completely converts the JSON into a monolithic LabVIEW structure. I suggest people think a bit more modularly in terms of "subJSON". The first question I would ask you if I were working with you on your actual project is why do you need (at this code level, at least) to convert your variables from their perfectly reasonable JSON format to an array of clusters?
    1 point
  3. Here is version 2. As far as I know, there are no issues with it Requires LabVIEW 2019 or later. Not compatible with earlier versions. Y Controls Support - Version 2.0.0.0 Installer.zip Y Controls - Version 2.0.0.0 Source.zip
    1 point
  4. Do you have access to any hardware? "Technical task" is a bit vague... A few years ago I started playing around with https://projecteuler.net/ It was a fun way to practice algorithms with LabVIEW, I think I solved the first 50 or 60. I'm not sure if this is "technical" Any idea on what you like to do? Any special interest? What's your course?
    1 point
  5. Seems VIMs can no longer be used in polymorphic VIs either. I don't think this is a good idea. The VIMs I've played around with (before the type case structure was introduced) relied on at least one terminal having a type which would dictate the undefined types due to the nature of the internal polymorphic VIs (like a Queue or DVR). This is why I was trying to get a VIM to create a DVR which "should" define the type across all connected VIs which would solve this problem. In a nutshell, I'm expecting this set of VIMs (rightly or wrongly) to behave like the Queue, Notifier et. al. primi
    1 point
  6. I can't find them in the examples finder (tried a few different words). The button on VIPM shows the directory with them, though. FWIW. I hate the example finder. You neeed to know the right words for what you're searching for and it's a lot of clicks and typing to get there (ignoring the excrutiating pain of actually creating the Example Finder special files). It's much preferable to have them in the same pallet as the VIs; as you had originally. They need to take that requirement off of the tools network checklist.
    1 point


×
×
  • Create New...

Important Information

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