X___

It appears that the Green Lady of NI has moved to even greener pastures: IBM - Biographies Can't abbreviate IBM (I?) but the website could use some of that pastel green and washed out pink palette NI has ambitiously engineered his website with.

I am not sure there is any special functions in the MKL (at least I could not find any in the description) and all these are LV_something in the DLL call. There is really no wrapping to be done here, as the arguments are only a few. So maybe after all NI did code those (sometimes using lousy algorithms, as was the case for the Kummer function)...

Similar to the VI posted at the end of the blog post 3 above (with less granularity and the option to do the reverse by mistake! :-) In what sense is the project-level check box not working? I am interested because I have set the app-scoped flag to "remove compiled code" but still occasionally find some new VIs (created by "Create sub VI from selection") with their flag turned OFF. It is probably time for me to ask whether I am just victim of a LV virus or this is indeed a reportable bug (very irreproducible, so not very convincingly reported).

<OOT> In the case of the Kummer function (which I was referring to above), this appears to be an internal algorithm as the function is called LV_Kummer (there are a number of similar LV_functions in the lvanlys.dll). For the purely MKL ones, I guess we have to check the bug fixes here (without knowing which one is relevant for which LV version...): MKL Bug Fixes </OOT>

<DEBUG_OUTPUT> 3/12/2021 10:42:37.511 AM DWarn 0xFCC058F4: An item recompiled in the final iteration should not still have recompile needed set: [VI "ix.vim" (0x0000029f40dbd0f0)] e:\builds\penguin\labview\branches\2019\dev\source\compiler\compiler.cpp(621) : DWarn 0xFCC058F4: An item recompiled in the final iteration should not still have recompile needed set: [VI "ix.vim" (0x0000029f40dbd0f0)] $Id: //labview/branches/2019/dev/source/compiler/compiler.cpp#6 $ First comment: the penguin has reared its ugly head (or tail) again! I do not have a E: drive on my PC, so this is probably some internal stuff, as is the //labview/branches/... thing. The ix.vim is mine though and while not doing what I want, it looks pretty innocuous:

Kind of out of topic, but if confirmed, that transposes the source code source from NI to Intel... MKL forums seem to be indicating that obtaining source code from Intel is a complex and costly proposition. I wonder whether this is why it took 2 years to fix a numerical bug in LabVIEW (i.e. this was out of the hands of NI and had to be fixed by Intel): https://forums.ni.com/t5/LabVIEW/Bug-in-the-Kummer-Function/m-p/2387522

I learned about the Project-level "Mark Existing Items" button reading that blog post...

Project Dragon LabVIEW: Announcing Project Dragon - Managing LabVIEW Virtual Environments with VIPM - YouTube Project Dragon Sign Up - VIPM 2021 (jki.net)

It was not free and indeed was carrying along a few MB of extra payload in each executable/distro. That link will not be usable by new users (as far as I understand) since they don't sell licenses anymore.

What is the problem? As far as I remember I just had to tweak a path constant... However this is more than python. It's python in a Jupyter notebook (which is getting very popular in many circles)

Sounds good. Will try.

I have my suspicions. But I like the terseness of the warnings (which pop-up only upon restarting LabVIEW). I suppose there is not more info that can be provided to the user (the LVInternalReports are binary files, so I can't make much of them).

The last time you ran LabVIEW, internal warning 0x occurred in image.cpp.

Appropriately enough, I recently got this startup warning as well: The last time you ran LabVIEW, internal warning 0x occurred in xstuffprivate.cpp.

Anyone has had to deal with this type of warning and know how to handle them? I have communicated the associated report several times but have now given up as I am sure NI does have better things to do (say bug fixes). LV 2019 SP1 64-bit on Windows 10.

From the foreword of Doom's book: "You owe me a shipped game every week, and if you don’t ship, you’ll get an F." Three classes and 127 games later, almost all of my students went on to jobs in the game 13 industry, no mean feat with a game design degree, and many of them credit the painful time constraints of the class. Terror works. I recommend it." I wonder how that applies to IDE development :-)?

I am reading through that lingo and am trying to extract the substance. What I read is that she was hired by NI for a specific job, did (or not) do it and was, if not fired, at least forced into a situation which led to her resignation after about a year on the job. That sounds rather short to me, but it is true that I am not privy to the way things are working on modern corporate boards. Maybe that is the new trend. I suspect there is more to it, and that her opinion that the business was run in a very outdated manner (saying that on a podcast sounds to me very non-politically correct) may have been the main reason. After all, her title is/was Chief MARKETING Officer, not Chief OPERATING Officer. Then there is the question of whether the "Good Ol' Boys" club might have reacted unkindly to a female outsider (I am not clear what her Dell and Rack Space background means in terms of her tech-savvyness. After all, she appears to have a BA in architecture and seems to only have held marketing positions).

A new chapter in the NI saga? Found in a recent SEC disclosure (I was trying to figure out whether the slow increase in NI stock value since last November was due to something else than the recent announcement that they were firing 10% of their employees to increase the shareholder happiness): "On January 3, 2021, Carla Pineyro Sublett, the Company’s Senior Vice President, Chief Marketing Officer, and General Manager of the Portfolio Business, and a named executive officer, notified the Company of her intent to resign from the Company, effective February 1, 2021, to pursue other opportunities." Who is Carla? Well, she is Mrs Super Green in the flesh: Carla Piñeyro Sublett - NI, first ever Chief Marketing Officer for NI. Intrigued, I looked around and found a couple of (moderately) interesting podcasts: Carla Piñeyro Sublett - Top podcast episodes (listennotes.com) in which she sounds like a very capable lady, and confess that she "discovered" that the company was in need of not just a rebranding (which she carried out brilliantly, we will all agree) but a complete reform. Her decision seems to indicate that that opinion might not have sounded too great to her top brass colleagues... I want to believe she was sincere when she says (said) that her customers are amazing people (a little bit emphatic, are we not?), and that they should be empowered (hence the picture of someone I assume is a customer "engineering ambitiously" on the landing page). I am not sure whether that meant "listened to", but if that was it, she definitely was onto something. NI: if your customers don't think you have what it takes to provide them with the tools they need to stay on the top, what do you think will happen? And if you don't want this to happen, what do you think you need to do?

Consider yourself lucky. It could have been all green... super green.

Are you forcing a conflict with Martijn Jasperse's H5labview package, or is this something made up by VIPM?

Free is maybe pushing it. Zero technical support without a SSP would be an appropriate model associated with open source. Of course this wouldn't prevent a vibrant community support (independent from NI) from existing, but this is not what the big industrial companies using LV would go for. They would remain NI's proverbial cash cows. I think the misunderstanding on the corporate side of why open source is beneficial for code safety and reproducibility is understandable, as I can witness the same ambivalence if not resistance in academia. As for NXG and webUI (or whatever they call it now), as discussed elsewhere, it looks like NI doesn't have the resources to bring the vision (whatever it was originally) to fruition, and their recent decision to abandon it will probably lead (or has already led) to morale cratering and talent effusion, so I wouldn't hold my breath... One thing I'd add to the list is this: stop the yearly versioning breaking backward compatibility. This is frankly moronic and the clear and only reason why this exists is NI pricing scheme. Adopt the scheme suggested in the first paragraph and this can go right away.

Sounds like King Louis the XIV's court. If someone had just pointed out that the natural next step of such an IDE was to introduce "text shortcuts" to diagram objects, they were quite a short distance from reinventing a text-based programming language. Brilliant!

Yeah, well, when was the last time NI asked users what they were expecting in a IDE UI? Or what they did or did not like in the mock up designs they were cooking up? I am sorry, I forgot about the "Idea Exchange" forum, which had so many transformative effects on the development of subsequent LabVIEW versions... Of course, ultimately this is probably not what killed NXG (the dislikes of a few old geezers for the IDE).

Following paul_cardinale's review of my demo, it turns out there was no glitch after all (well, in my understanding or attention level, maybe).

Sent as a PM. Also, is there a way to drop a Y Control in an array (or cluster)?