X___

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:

And StarLogo TNG (The Next Generation)... the ancestor of MIT's App Inventor. After all, NXG is supposed to be so simple that everyone can use it, right?

Whatever. My question was: did I understand correctly that individual VI files shared between projects were going to become hard to use. The answer was no. I then commented that in this case there was nothing new of interest, or at least I could ignore the the gll paradigm. As for picking a fight, why would I even bother. As you know, I left NI forums after you (AQ) summoned me by private message to stop expressing critical comments. There is a difference between engaging customers and addressing their needs, which I believe is something that would benefit from some soul searching on NI's part. As for me, I have no interest in wasting any time with NXG until I am forced to abandon CG. I hope that by then I will be sufficiently proficient using other programming environments that are open, free and supported on all platforms.

Then I am completely convinced that I have nothing to add to that discussion (which I guess was the purpose of this enlightening statement).

Thanks, this perfectly clarifies the matter. Nihil novi sub sole?

Am I reading this right?

It's a start. Humor and the recognition that the world is moving on outside the ivory tower...

It is a different product. It's like if a car company messed up some component and said: sorry, we fixed it the new model. But, hey no ill intent here, just a business model.

It's like moving the Expression Node back in some subpalette of the Mathematics functions that is not existing in the Base LabVIEW version (https://forums.ni.com/t5/LabVIEW/Expression-Node/td-p/3974820). Completely uncalled for, but, hey, AQ doesn't think that text-based mathematics should even be allowed in LV, so what do we know?

Can't use it with 64-bit LV, AFAIK...

Actually, the nipkg.ini is in \ProgramData\National Instruments\NI Package Manager\Settings\nipkg.ini

Can't get that to work systematically. Sometimes it does the trick, sometimes it doesn't. I believe this is worth reporting as a bug. While this could be a wrong hunch, I wonder whether this might be due to the narrow scrollbar width in the NXG graph legend. Notice that it is narrower than that of a NXG array (shown on the right below). It is definitely narrower than that of the silver style graph legend (shown second from the top left), which is narrower than the modern graph legend (shown last on the left). The latter is of the same width as the classic graph legend. The reason I am suspecting this is that I have seen something similar in a utility that was supposed to return the clicked element in an array (https://forums.ni.com/t5/Example-Code/Determine-Clicked-Array-Element-Index-in-LabVIEW/tac-p/4040339/highlight/true#M14360) and failed with silver and NXG arrays because the border sizes and other details of controls have changed from style to style, and the underlying routines have not been updated. In any case, this is annoying enough to be reported.

That was a trick question.

OK. What is the idea of password protecting those CLN and not, say, those in the Analysis VIs. Are we at risk of blowing up the planet?

Are you sure of that? The hierarchy shows System Exec call, so it might be even cruder than a .NET call indeed:

The NI_Unzip.lvlib VIs are all password protected (probably because underneath, they are using some .NET calls they don't want people to mess up with). So yes we don't know what they do, although the help tells us what they can't do: Unzips the contents of Zip file to the Target directory. Set Preview only? to TRUE to preview the list of files in Zip file before you unzip the zip file. This VI cannot unzip a zip file that is password protected. Why wouldn't it support password protected archives? Anyway, the compression/decompression algorithms are not necessarily particularly well described or unique for that matter and it is therefore not surprising that some implementations might be incompatible (although they shouldn't): .NET documentation https://docs.microsoft.com/en-us/dotnet/api/system.io.compression.deflatestream?view=netcore-3.1 An old 40,000 ft description: https://zlib.net/feldspar.html quoted in this interesting "from-the-ground-up" implementation (quoting the previous reference): http://www.integpg.com/deflate-compression-algorithm/

It does seem to do exactly what I needed though, which was emulate that piece of MATLAB code: zipbuf = fread(fid, offset, 'uint8=>uint8'); tmp_dir= tempname; [SUCCESS,MESSAGE] = mkdir(tmp_dir); if SUCCESS fnz= fullfile(tmp_dir,'temp.zip'); else disp(MESSAGE); error('Cannot create folder.') end tmp_fid = fopen(fnz,'w'); fwrite(tmp_fid, zipbuf); status = fclose(tmp_fid); fnu=char(unzip(fnz,tmp_dir) ); tmp_fid = fopen(fnu, 'r'); data = fread(tmp_fid, length, type_str); status = fclose(tmp_fid); [SUCCESS,MESSAGE] = rmdir(tmp_dir, 's'); if ~SUCCESS disp(MESSAGE); error('Cannot delete folder.') end end

A simpler way might be to do this using native LV functions: Of course you need to create two temporary files, but this is year 2020...

Ah Ah ! I had noticed this "non working scrollbar" thing for a while, but couldn't find the time to investigate the nature of the problem. I had also figured that the mouse wheel worked, and indeed I play with the visibility as you do. Thanks for nailing it. Now write the simplest standalone VI you can that demonstrates the problem and please file a bug report with NI (https://sine.ni.com/srm/app/newrequest), answer the questions of the engineer who will contact you and let us know when you get a CAR number. Or if that is too much to ask, let us know and I will do it (you will need a current SSL to be able to file a support request). As Hoovah said, Graphs are bug-ridden and have for eons and with NXG around the corner decade future, I wouldn't hold my breath for a fix. But who knows...

There will be Ph D thesis written on the Boeing MAX debacle. I am starting to wonder whether there will be, regarding the NXG one, if no insider information ever leaks out. In the meantime, some food for thoughts: https://medium.com/@herbcaudill/lessons-from-6-software-rewrite-stories-635e4c8f7c22