Jump to content


  • Content Count

  • Joined

  • Days Won


Dataflow_G last won the day on June 18 2020

Dataflow_G had the most liked content!

Community Reputation


About Dataflow_G

  • Rank

Contact Methods

LabVIEW Information

  • Version
    LabVIEW 2018
  • Since

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. To add to the list of potential red flags: Windows Registry Access VIs VI Scripting calls (deleting or subtly modifying existing project code) Large VI file sizes / large constants (malicious VIs stored as byte arrays, so avoiding VI Analyzer's checks) Bugs known to crash LabVIEW Shortened links in VI help Non-standard block diagram colors (hiding a subVI on an identically colored BD) Obfuscated code (strings masquerading as boolean arrays, numbers with hidden precision, etc): Very small subVI icons (think a VI disguised as a
  2. Here's some more rebrand info I found by one of the design companies behind NI's rebrand, including a mock-up of a green PXI with an interesting font choice (I'm pretty sure that's a Q).
  3. I don't mind the new green on the landing page of ni.com, but elsewhere on the site the new theme is a bit too much. I wanted to fix the near invisible links that @LogMAN ran into, but got a bit carried away: If anyone is interested in using the blue style, you can download it from here. Be warned it's not perfect, there's still lots of green bits on mouse over etc, but I find overall it makes the site much more readable. If blue isn't your thing, the primary color can be changed by setting the root --forrest-green color to something else.
  4. There is Stylus which is a malware / analytic free fork of Stylish. BTW, did your avatar succumb to the rebrand too?
  5. The logo is pretty uninspired and looks lifted from this company. It's going to take some time to get used to the green theme too - in my mind NI = blue + white. I wonder if NXG will get a green coat of paint. I'll reserve judgement on the content until I've seen the webinar, but it's heavy with cringe worthy marketing speak. Also, a moment of silence for Nigel the NI eagle. Soar Ambitiously™, N 🦅
  6. The very first comment in that thread is interesting. It's no coincidence NXG looks like LEGO Mindstorms NXT. There was an R&D project in 2009 called LabVIEW Notebook Pioneer. You can see it here - video 1, video 2 and a screen cap: It looks like a very early NXG concept (single window, panes, docked palettes, data stored with project, etc). What's interesting is Christina's comment in the linked blog post. It would seem NXG's roots were partly influenced by NXT. Not saying it's good or bad, just interesting that it was picked up on.
  7. Hmm, it seems the difference in resolution of primary vs secondary displays is being added to the maximized window on the secondary. In this case it's a difference of 640x320 ( or 2560-1920 x 1440-1080). If those numbers are then subtracted from the window bounds when the title bar isn't visible, they're within 1px. Looks to work for your resolutions and results too @nikp. Might be a better solution than toggling the title bar.
  8. I'm seeing the same issue as @nikp, where the window bounds for a maximized window on the second display are way off. It looks to be related to whether the title bar is visible or not. There are two displays in a side-by-side configuration, the primary is 1920x1080 and the secondary is 2560x1440. Running under Windows 10 with display scaling off. I tried the examples posted in the thread @LogMAN linked to with very different results. @hooovahh's version worked for both displays, while @Aristos Queue's version only had correct results on the primary display. After trying to work
  9. Thanks. It was mostly to satisfy myself I wasn't missing some game changing feature or workflow in NXG that was hidden behind its slow and drab exterior. Like you, I haven't seen any examples of large projects running under NXG so wanted to document at least a small project. There was one NXG product owner who saw it and took the time to respond, and noted the event structure feedback was useful. I think it had some support for clusters of clusters (see Neil's example), but definitely not for classes and references. Here's a few more issues that I ran into: Ther
  10. Thanks for putting down all your thoughts and providing examples, Neil. I agree with every point you've made. Have you used the Shared Library Interface editor yet? That's some next level UI inconsistency. I wrote a couple of blog posts on my experience converting a small (< 100 VIs, < 10 classes) LabVIEW project to NXG (see Let's Convert A LabVIEW Project to LabVIEW NXG! Part 1 and Part 2). During the process I made a lengthy list of issues and came to the same conclusions many people have voiced in this thread. Of the issues uncovered during the conversion, some were due to missin
  11. Out of interest, what are the MD5/SHA1 hashes of the problematic lvanlys.dll? I have a LV2019 SP1 64-bit install (via NIPM, not the offline iso), and analysis functions are working. The copy of lvanyls.dll I have match the file size and modification date in your screenshot. Its hashes are: MD5: 8b57b1ab47c00387b370d3d0fac0a246 SHA1: 7d45297d3e1d10f1de5960c116c58b7dc186fd2e
  12. Some more LabVIEW from the past, this time from The Minnesota Apple Computer Users Group newsletter, mini'app'les (December 1989). "Hubba, hubba, hubba!" Mini'App'LesNewsletter1989-12.pdf
  13. Here's a review of LabVIEW 5.0 from Macworld magazine, July 1998. "It's gigantic---a typical installation might involve 200MB of support files and programs"
  14. I assume you meant this video? There is this older video of Dr. T and Jeff K. introducing a LabVIEW Basics Interactive CD-ROM (~LabVIEW 4), but it's not as exciting as the LabVIEW 5 promo.
  • Create New...

Important Information

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