Rif.: uiconv queuing uir files

[Pims]

Hello,

It's been a long time since I've touched our code that uses this tool.

The looping call is not a problem.

I think the tool hasn't always been updated over time.

Even in 2017, it should work. Afterwards, I think some options don't work as they should (options <> in manual).

I had opened a ticket with N.I. (without having received a real response) ... it was already the end of CVI.

Have you tried completing your code with the options suggested by A. Carlox?

-silent: run silently - input file, as well as output .c and .h files must be specified 
-skipBuild: don't build target files after they are generated 
-outputToStdio: output to STDIO 
-stdioVisible: make STDIO visible
-noOvr: don't overwrite target files if they already exist 
-noSkipDflt: don't skip default attributes 
-noCommentSkipped: don't skip attributes as commented code (applies only when noSkipDflt is not passed) 
-initVars: init variables to zero 
-noErrChecking: don't include error-checking 
-noUseErrChk: don't use "errChk" macro (applies only when noErrChecking is not passed)

 For example with "-silent" ?

"%CVIDIR%\bin\uiconv.exe" -f "%CVIPROJDIR%\test.uir" -s "%CVIPROJDIR%\test.c" -i "%CVIPROJDIR%\test.h" -silent

Good luck, and don't hesitate to let me know. If it doesn't work, I'll run some more tests.

[AllenInIowa]

No luck with the version that came with 2017. It does not seem to have the command-line options. I even loaded the .exe into a hex editor and cannot find any of that text.

But I downloaded the 2020 installer (demo for 7 days) and looked at the .exe in there. It does respond to the command lines.

However, it will generate a 0K file. I have not gotten it to work yet. Even manually browsing to a panel does not appear to work (maybe missing some other component that needs to be installed?).

Results: I can use the 2017 version manually and get it to work, but no command lines.  The 2020 version does seem to have command lines (they populate the boxes if you omit -silent) but they do not produce files properly.

It was worth a try 😉

[carlox]

I think it's related to the CVI runtime.

You could try downloading the 2020 runtime, maybe just installing the side-by-side version, and see what happens. I don't think even the shared version will break the 2017 installation. I

f there's one thing the guys at NI were good at, it was backwards compatibility, so I think CVI 2017 will work (maybe even a little better) with the 2020 runtime. You can try on another PC to be sure.

P.S.: are you absolutely sure that your license does not allow 2020?

[AllenInIowa]

---

P.S.: are you absolutely sure that your license does not allow 2020?

---

Confirmed. We only bought LabWindows 2017.

I will check with the Run-Time. In the past, "something" had upgraded the runtime to 2020, but now as I check, I cannot figure out where to even tell which runtime is installed.

[Pims]

Hello,

Even today, in CVI 2020 (f4), we regularly use the code created in 2020 around this tool (uiconv.exe).

We use it very often to convert our (.uir) files into (.h) and (.c) files, then, we recreate from them, a (.ini) file,

almost equivalent to the (.tui) file ... discovered too late.

It's very convenient.

On my side, the tool always generates something.

Some options (per argument) are not correctly fully fonctional,

and do not give the right content, inside the (.c) file.

I found my ticket at NI (01608625 - 27/06/2022), it said:

    Mode "silent" of uiconv.exe, options not functional

        If I use the mode "-silent" with also "-noErrChecking" options, of the "UI to Code Convertor" N.I. software (uiconv.exe),

        the "C" output file generated is not correct :
        ...\uiconv.exe -f "%s" -s "%s" -i "%s" -noErrChecking -silent
        Without the "-silent" mode (but with the "Generate Code" button), the "C" output file is correct :
        ...\uiconv.exe -f "%s" -s "%s" -i "%s" -noErrChecking + "Generate Code" button by user

Be careful, this tool needs LabWindows/CVI installed.

Because it opens LabWindows/CVI quickly, and loads the (.uir) file, to create the 2 files (.c/.h).

See my code extraction and comments (make in 2020) (if that helps).

[AllenInIowa]

Thank you for your responses.

It looks like we are out of luck. With no command line support on the old LabWindow version we have, and no plans to pay $$$ to get the latest old 2020 version, my only option is do to it manually for each of the hundred panels, or figure out the -86 error I am getting using the method that lets me use the .uir files in LoadPanel():

https://forums.ni.com/t5/LabWindows-CVI/Building-LabWindows-2017-GUI-using-Microsoft-compiler-Error-...

[carlox]

As a suggestion, you could use the 2020 trial version to do the conversion, maybe installing it on a virtual machine to have the possibility to reset everything and start over if you still need time. I think using the text version of the panels is the best way, because starting from those sources you could write, if you want, a converter in the standard Windows dialog format. What you will get may not be aesthetically beautiful, but it will be just a starting point to fix them with a standard dialog editor.

Just my two cents...

[AllenInIowa]

---

@carlox wrote:

As a suggestion, you could use the 2020 trial version to do the conversion, maybe installing it on a virtual machine to have the possibility to reset everything and start over if you still need time. I think using the text version of the panels is the best way, because starting from those sources you could write, if you want, a converter in the standard Windows dialog format. What you will get may not be aesthetically beautiful, but it will be just a starting point to fix them with a standard dialog editor.

---

We would rather avoid any legal issues using a "demo" version to create commercial products 😉

[Pims]

Hello,

I compiled my project in LabWindows/CVI 2017 and encountered a fatal Windows error,

when I pressed the button (without "-silent," so you have to press the "Generate Code" button).

I tried changing the checkbox options, before pressing the button, but without success.

If I do it manually with 2017 version, there is no problem.

Without CVI licence, I believe that the executable is time-limited.

Sorry.