Good things from NXG that I would like to see brought over to LabVIEW classic

[TroyK]

As suggested by EricR in the "What's stopping you from switching..." thread.  Here is what I liked in LabVIEW NXG that I would like to see brought over to LabVIEW classic (now that NI is ceasing development of NXG in 2021).

For me it would be:

• vector based user interface objects that I can create and edit myself using svg
• A slick UI (and add dark mode 😉)

What would you like to see brought over?

[altenbach]

I sure hope that the NXG data grid will make it (See also)  

[JimB.]

May not exactly be on topic since I don't think they ever made it out of the backlog, but I was really disappointed when Darren said sparse enums would only be coming to NXG.

[cbutcher]

I'd like to see some of the namespacing changes make it to LabVIEW 202x. Being able to set the namespace of code in different ways seems like it would be pretty useful for some of the packaging/distribution challenges currently being tackled.

[wiebe@CARYA]

Unicode

[wiebe@CARYA]

Dynamic controls\indicators!

[wiebe@CARYA]

Documented API for custom:

• Functions
• Tools
• Diagrams
• Project items

In fact, CG should move to NXG's mindset: "here's how to make tools, please do".

Verses CG: "it's unpractical as it is, and we locked it with hashes on top of that".

[wiebe@CARYA]

Readable file format (XML or JSON would do...).

[wiebe@CARYA]

A zoom in.

They can keep the zoom out 😋.

We need to be able to make things bigger, to see 1 pixel wires on 8k screens (16? 32? Who knows?). As long as the zoom factor stays >1X, we're not encouraging one liner VIs more than we do now...

[wiebe@CARYA]

I could get used to the direct access of properties of the selected item.

But please not in a docked window, permanently wasting screen resources...