08-29-2025 02:13 AM
Why was Multiple Variable Editor removed ?
am i the only one who have projects with many shared variables and stupid enough to use the DSC database for data logging
export/import is always a hassle with CSV with comma as the separator and excel as editor for us euro guys
is there a way to make the deliminator ";" in labview ?
08-29-2025 02:25 AM
Hi TandM,
@TandM wrote:
is there a way to make the deliminator ";" in labview ?
Yes.
Just set the delimiter at the WriteSpreadsheetFile function correctly!
08-29-2025 08:47 AM
Hi TandM,
Apparently the Multiple Variable Editor has been removed for no apparent reason starting from LabVIEW 2024 Q1:
That's indeed a shame, as no practical alternative is given appart from import/export from/to CSV.
The only way that I can think of would be to code your own tool that reads/writes the CSV.
@GerdW wrote:
Hi TandM,
@TandM wrote:
is there a way to make the deliminator ";" in labview ?
Yes.
Just set the delimiter at the WriteSpreadsheetFile function correctly!
The OP certainly refers to the built-in project library right-click options "Export Variables..." and "Import Variables...", which indeed, exports/imports only comma-separated strings.
08-29-2025 09:51 AM
Hi
Rolf once gave a reason why QT was used in LabVIEW.
So maybe NI now decided it did not want to license it anymore. Just guessing :
https://lavag.org/topic/6892-use-of-trolltechs-qt-in-labview/
QUOTE(brent99 @ Feb 22 2008, 05:08 PM)
I saw that, and just assumed that Labview IS written in QT (at least as of v6.0 or so). No?
No definitely not! The entire UI widgets have been written for LabVIEW 3.0 from scratch based on the drect windowing API of the spcific platform (X11,Windows GDI and Mac OS QD) and that hasn't changed at all until now. The only real modification was with the adding of the 3D types of controls in LabVIEW 6, but they are based on the same proprietary object model that is used for the other built in LabVIEW widgets.
QT appearently only is used for the Multiple Variable Editor that is part of the LabVIEW Data Logging and Supervisory Toolkit, but since the LabVIEW installations contains that anyhow (but the according license is necessary to enable that functionality) it comes with every standard LabVIEW installation and since it is in the executable directory, Windows will always prefer to load those libraries if some component such as the SCC API provider for said system needs to load those libraries with that specific same name.
Rolf Kalbermatter
Regards
09-03-2025 03:48 AM
thanks for the answers
I worked my way around with the export/import hassle
09-03-2025 08:28 AM
@TandM wrote:
export/import is always a hassle with CSV with comma as the separator and excel as editor for us euro guys
is there a way to make the deliminator ";" in labview ?
Especially when the , delimiter clashes with the decimal point defined by "system decimal point"