X___

That's working well enough. Now we need to convince github and other repository cloud storage solutions to run this on their servers...

The binary-no preview nature of LabVIEW code is obviously a problem.

Note that the discussion was not about whether or not LabVIEW is on its way to dominate the landscape, but where it is discussed (both are certainly related).

Are you seeing things between the lines? LV is not present among the first 50 listed... In case that helps shedding some more light on reality, here is yet another recent list essentially saying that LV is nowhere to be seen on Github or Stack Overflow: https://redmonk.com/sogrady/2020/07/27/language-rankings-6-20/ and I am not talking about the list itself, but the graph shown here: doesn't list LV, as far as I can tell. Now I am sure that if you limited this kind of analysis to NI's website or LAVAG, LV would hit top of the list in both cases...

https://www.tiobe.com/tiobe-index/ LabVIEW dropped below 50... Might it be that its rank follows its average user age?

That's the only thing I had noticed... as overdue (although of no use to me).

That looks insidious indeed. It definitely doesn't work this way in 2019 SP1. This is the kind of mental note (close LV and restart to clear up memory) I would certainly forget every now and then. I am refraining from upgrading without pressing reasons, since chances are I will lose access to support for old NI hardware I haven't replaced yet (by non-NI ones, of course!). I realized too late I should have stuck to 2018 SP1 for hardware reasons (and as I described recently in the thread you linked to, because of a newly introduced project explorer bug among others). 2020 seems to be one of those years we will try our best to forget about ASAP...

CAR# 1096546 was submitted for this bug

Parallels has a few bugs up its sleeves too, so I am willing to lean toward that conclusion too considering that no one seems to have observed this. Is anyone using Parallels Desktop in "Coherence" mode and observing this phenomenon? There is no Windows' real estate per se in this mode, each Windows app's window appears as a regular macOS one (with the Windows style though), so I can't really imagine that the OSes could be mislocating the cursor... but this is all beyond my technical knowledge to really ponder. Thanks for looking into it though.

Frequently enough that in my drive to make this world a better place, I decided this was a worthy campaign to galvanize the crowds for.

No scaling enabled that I know of. I am using a VM in Parallels Desktop running on a MBP, but I would be surprised it is the root cause.

Here is the video illustrating the symptoms. Of course the demo effect wants that the first time I try to drop the subVI, the cursor looks fine (I had just verified on a brand new VI that the symptom appeared right away, and after I went through the recording hoops, I had to "work" for it to show up), but a brief excursion with the cursor over the project (from which the subVI came, so indeed I could not drop it again in there) was enough for the cursor to turn back to the "forbidden" icon. I am not sure that is very visible in the video, but there is a little bit of a "stuttering" and you can usually very briefly see the arrow+ cursor alternating with the forbidden icon. The bottomline though is that I cannot drop the subVI in most of the virgin diagram and have to actively search for allowed drop zone. I have come to get used to it now, but it is definitely getting old and a productivity hog. Problem Dropping a subVI.mov

The title is made up, but explains what I have been experiencing for years, hoping that it would be fixed in the next version, but it never has, so I am starting to suspect nobody is caring or possibly maybe nobody even noticed it? Anyway, the symptoms are: when I drag a VI (from either a palette or from the icon of an open VI) into a target VI's diagram, I am frequently encountering this odd and annoying 🚫 symbol where my cursor is (it's not red and it is slanted the other way, but this is the closest emoji to the real thing I could find), instead of the "androgynous" cursor (a mix of ♀️and ♂️) which tells me that I am going to copy that object where the cursor is. I would move the cursor around, seeing a 🚫 wherever I go, until I would fleetingly grasp a cursor with the + index (the "androgynous" cursor) over some random location, and then, painstakingly try to go back to that region to find the sweet spot (pixel really) where I am able to drop the VI. Of course, once dropped on the diagram I can move the VI anywhere where I was forbidden to drop it during my initial attempts. That's got to be the most annoying bug in a graphical programming environment ever... Am I the only one to experience this? I am using 2019 SP1 64 bit, but that has been around for several versions already.

I suggest you split the thread, as it may become confusing if everyone refers to a different bug. Mine has been submitted and I will report the CAR when I get one.

...and graphical programming (sorta)! With more funders will come PoE (page here) which would be cool. Where I learned about the Myriad-X vision processing unit (which the new green deal company, BTW, doesn't seem to know about - or the search box is broken?): https://www.intel.com/content/www/us/en/products/processors/movidius-vpu/movidius-myriad-x.html using DL (the page also refers to additional AI-related products).

I used to have a reputation to find bugs that nobody noticed...

I am using LabVIEW 2019 SP1 in Windows. I am trying to reorganize dependent VIs into virtual folders in a project. I have noticed that it is now impossible for me to drag an object in a non visible part of the project. It used to be an exercise in frustration management in the past (with a single pixel-wide sweet spot triggering a painfully slow scrolling of the project explorer objects' list) but it seems to have been solved brilliantly by completely removing the ability to drag and drop objects in non visible parts of the project... To clarify what I mean, here is a dummy project with empty VIs: If I now reduce the size of the window such as to hide the virtual folder and show the object I want to move into it: I can't trigger the window to scroll anymore (all I get is the "forbidden" icon instead of the mouse cursor, which tells me I am trying to do something that is forbidden: it is not. I can drag the object in the virtual folder if it is visible). Of course in this dummy example, I could expand the window to reveal the VF. But the point is that in typical situations, I have a (large) number of dependent VIs (or other objects) I want to reorganize in virtual folders, and my screen is not large enough to show both VF and objects. Now a workaround is to Add... (contextual dialog) each file into the virtual folder by browsing the File Explorer, but this defeats the purpose of the Project Explorer, which "neatly" groups files located in many different places into a single flat list. Now that I think of it, it might all be a clever plan to force us to abandon LV GC to move on to NXG... although I suspect it might not be easier to do there or completely different and counterintuitive. PS: I am using a VM in Parallels Desktop, so it could very well be a Parallels bug, but I wanted to check with the community whether I am missing something obvious.

These are pretty bold color-coded statements in these troubled times... Kudo to NI:

I got it! Fifth Element

And don't think of visiting the site not logged on... You will be granted by this very invasive splash screen, every time.

But it is a stylized P nis n't it? (Sorry for thr typoss)

What do you see beyond "package" and "manager" ?

The more I look at the center logo, the more I believe it captures exactly the kind of excitement generated by the whole operation.

Be so kind as to distill the substance of it in a post here.

I don't think the guy in the picture is going to be here in 100 years. Heck, I am pretty sure nobody at NI today will be here in 100 years. Come to think about it, NI might not exist any more then. So what a well thought-through slogan to put up on a landing page... Personally, I think this is way too much color for NXGNI. I fixed that for you: