GDS UML Modeller: Error 0x692 when opening UML files

[FrasseKatt]

Something happened last week. Suddenly, I can't open UML files with UML modeller; see attached screen shot.

When pressing the Open button, this dialog appears, the indicated File Dialog is high-lighted and then UMLEditor Main.vi stops executing.

The day before, everyting worked perfect.

I've tried re-installing NI GDS and opened a service request, but they can't help me. 

I also installed Open GDS to see if this bug was fixed, but the same thing happens.

Is there some way to fix this?

Is there some ini-file telling which file to open at start-up (as a workaround)?

[RavensFan]

It's kind of obvious.

The error has nothing to do with "UML Modeller", but the LabVIEW Dialog Box.  It says, "the string contains an unexpected null character".  I see that the match pattern string constant has a bunch of null characters in it.  It looks like it is set for \code display mode and has a bunch of \00 's in it which is the \code for hex 00.

Why are those nulls in there?  Read the detailed help for the file dialog and it will show you how to build the File Pattern input.

[FrasseKatt]

RavensFan, thanks for the input!

I've also suspected the match pattern string constant, but couldn't believe that a faulty string could get installed by the GDS installer.

However, this gave both me and NI a clue to the solution, simply edit this constant. But I'm also quite dissappointed that the NI Support didn't realise this until I told them what you told me.

[RavensFan]

---

@FrasseKatt wrote:

RavensFan, thanks for the input!

I've also suspected the match pattern string constant, but couldn't believe that a faulty string could get installed by the GDS installer.

However, this gave both me and NI a clue to the solution, simply edit this constant. But I'm also quite disappointed that the NI Support didn't realize this until I told them what you told me.

---

Sometimes us LabVIEW users out in the world have more experience than the support people.  😉

I just did some googling as something with nulls and separators for dialogs came to mind.  I found this:

https://forums.ni.com/t5/LabVIEW/Null-File-Dialog-Behavior-in-2019-amp-Forward-Compatible-Run/td-p/3...

I had replied into it last year, but I don't specifically recall it.  So the issue might be a carry over from an older version of LabVIEW.  But your issue seems to be directly related to this.

[FrasseKatt · Accepted solution]

Me and the support guy agreed on that editing the match pattern string constant is currently the best solution. Right now I use just *.uml.

However, he told me that NI would make investigation on this, which is fair as this shoudn't happen.

[oestay]

Thanks for this workaround. I got the same error. The original string was "*.uml)\00*.uml;\00Backup\sfiles\s(*.bak)\00*.bak\00\00" and I removed all the /00 and /00*, and my new string is "*.uml).uml;Backup\sfiles\s(*.bak).bak". Now this works ok. I use LabVIEW 2019 SP1 and the NI-GDS version is 1.1.87.94 (as my VIPM says).

[pcortes2]

I just downloaded the last version of NI-GSD (1.2.41.104) and same happened. They did not fix this bug.