So I've stumbled across the fact that LabVIEW 8.6 doesn't let me use more than 63 array dimensions like 7.1 (a friend uses it) did. (it also takes longer to open, but that's another story).
So what else is gone?
I am curious about the usefulness of more than 63 dimensions. Even if the size of each dimension is only 2, you will break all size limits. This means that at least about half of the dimensions need to be 1. So what's the point?
Not intending to act like a troll or hijack the thread, but I'm sure some physicist trying to make his math work might need more than 63 dimensions. Just sayin'.
I tried to make a 100d array back in about BV 2.1 and the diagram was comical, unitl I put a value in the array and it crashed.
I'll play along and mention the we used to be able to create a reference to the Cursor Palette that gave us complete control over what could be seen and we could customize it to our liking. See this thread to learn more about that one.
If I remeber any others I post them up.
BridgeVIEW's tag engine.
The CPU requirements did NOT scale with tag count and even 400 MHz machines could keep up with 5000 tags.
There used to be a white paper showing this fact.
How about some more "I miss" items?
Greg McKaskle - Now a Senior Architect (or better) in LV R&D used to answer questions here on the forum. It was nice to have him lift the hood regularly.
Dr. VI - Nice technical articles.
LV Challenges - Oh the fun we had trying to beat the crap out of our friends.
The ability to put a VI in the True case of a case structure with boolean Flase to include a VI in memory and simplify loading it at run time.
And since I am depressing myself with every item why stop with the current situation?
The CW 3D graph will of course not work on some platform and we will have to go to the new 3D picture version of the graphs where they seem to want to duplicate the data set about 10X before event thinking of rendering a pixel.
I suspect I am going to end up in a croner wimpering before the day is done.
The ability to use a VI in VI.lib that is NOT on the pallettes without fear that the next version of LV will kill your code (e.g. WE can no longer write a config file to disk without closing it.)
Where did I leave my towelie?
The ability to run an executable vi ( exe) without installing the runtime-engine or the VISA driver... just copy the lvrt.dll and the serial(??).dll one the same disk (something I don't miss, I prefer the stick 😉 ) and run your vi wherever you want....