Problems using LoadLocalizedPanel with CVI V9.0.1

[JürgenS]

Im using LoadLocalizedPanel function to use my application in different languages.

My application was created in CVI 7.0, then I created the lwl files to change languages. This App had multiple UIRs with miltiple Panels each.

Then I upgrade to V8.0 and I had no problems using this lwl files.

Since the upgrade to CVI 9.0.1 I use trees in my application. When I call to LoadLocalizedPanel I get "FATAL RUN-TIME ERROR: Dynamic Memory is corrupt" error. After many trials I modify with notepad the new lwl file and when I completely remove the entries of the tree controls, it works .

I checked also the correct path to the CVI 9.0.1 localui.fp. 

Are problems known when using trees in lwl files? How can I fix this problem? 

Many thanks for your opinions 

[JürgenS]

Has someone had a look at this behaviour?

Thanks 

Jürgen 

[Wetzer]

Hello Jürgen

So far i didnt find anything about Problems with lwl files and Tree Controls.

I will try to reproduce this issue as soon as i get my hands on CVI Version 7.0.

Have you tried to use lwl files created in CVI 8.0 in Version 9.0.1?

Regards 

Moritz M. 

[JürgenS]

Hello Moritz,

thank you for your answer. I tried to use lwl files created in Version 9.0.1.

Even now, I discover that the problem only occurs if the debugging level is set to "extended" or "standard". If the debugging level is set to "No run-time checking", the problem did not occur. 

Kind regards

Jürgen

[JürgenS]

Hello,

I think there is a bug in the LoadLocalizedPanel() function. If the lwl file contains a tree with a maximum of 7 columns, it works great. But if there is a 8th column (or more), the runtime fatal error "Dynamic memory is corrupt" occur if I try to load the panel with LoadLocalizedPanel() .

Here is the section of the lwl file:

[MAIN_MAIN_TREE]

Type = 10

Cols = 8

Items = 0

Flags = "EeffEfffEfff@f"

NumItemValues = 0

ColLabel_0 = "Date"

ColLabel_1 = "Time"

ColLabel_2 = "Plaintext"

ColLabel_3 = "Text1"

ColLabel_4 = "Text2"

ColLabel_5 = "Text3"

ColLabel_6 = "Address"

ColLabel_7 = "Testi"

If I use the Colum: ColLabel_7 = "Testi" (or more columns) the problem appear.

The problem is that I need many trees with more than 7 columns .

Could anyone help me please? 

Kind regards

Jürgen

[nickb]

Hello Jurgen,

I just wanted to let you know that I have reproduced the issue you are seeing, and will be filing a bug report on it soon.  I will take some time to look at the issue more closely tomorrow to determine if there is any kind of workaround we can suggest.

More information tomorrow -

NickB

National Instruments  

[nickb]

Hello Jurgen,

I had another chance to look at this this morning, and have filed a bug report for this issue with bug ID 173689.  From my initial investigation, I may be able to offer a workaround (hacky though it may seem) that should be sufficient until we are able to officially fix the issue.  I noticed from you .lwl file snippet that you are not translating any items in your tree, only column labels.  Based on what I've seen of this bug so far, I think that if you were to translate one tree item as a dummy (either translating and then making it invisible, or applying the same translation for all languages), you should be able to get around the error you are seeing. 

Please let me know if this is not the case

Sorry for the inconvenience!

NickB

National Instruments  

[JürgenS]

Hello NickB,

thank you very much for your efforts. I have followed your instruction (translation with one tree item and then I have programmatically removed this item) and it seems to work correctly . It is not a perfect solution, but it is a solution. I will track the reported bug ID and I hope there is a solution in the near future?

Once more thank you very much. 

Kind regards

Jürgen