Rif.: Multicolumn Listbox not editable after building to .exe

[Falc0n]

I created a program for measurement in LabVIEW. I use a Multicolumn Listbox as a control to enter temperature range and step parameters. It works very well in the development environment, but after I build the program into an .exe file, I can no longer edit or change the temperature range.

Why is this happening, and how can I fix it?

[pincpanter]

What about posting a super-stripped version of your project, exhibiting the issue? Preferably for LabVIEW 2021 or earlier.

It's very difficult to guess anything, without the code.

[Falc0n]

I use this Multicolumn Listbox to create a range of parameters, and I can change these numbers in the development environment. However, after I export the program to an .exe file, it becomes impossible to change the numbers.

 

[PalanivelThiruvenkadam]

You cannot edit MCL during Run time, Doesn't matter whether you are running a code or exe.

You Need to set Edit using Mouse click event

Check this out:

https://forums.ni.com/t5/Example-Code/Edit-Type-in-Multicolumn-List-Box-During-RunTime/ta-p/3681771 

[pincpanter]

---

@Falc0n  ha scritto:

I use this Multicolumn Listbox to create a range of parameters, and I can change these numbers in the development environment. However, after I export the program to an .exe file, it becomes impossible to change the numbers

 

---

Righ-click on the control and check Editable cells from the context menu. Save and rebuild.

Moreover, there is a property named Allow Editing Cells to turn on/off editing

[altenbach]

Seems you are editing these values in edit more while the program is not running, then run the VI, right? (Once you press "run" it will be too late to edit anything).

Can you explain the overall code architecture and the purpose of this code?

A stopped program should not even exist in a built applications (nothing to do with "export").

Can you explain while all these inner FOR loops have waits in them? There is nothing that requires any delay.

All your value property nodes should be local variables. (if you want to keep them as property nodes, at least combine them with the existing ones! (see picture)

I have the nagging feeling that the entire inner code could be dramatically simplified!

And yes, you can make the cells editable, but that seems dangerous.

[altenbach]

---

@altenbach wrote:

I have the nagging feeling that the entire inner code could be dramatically simplified!

---

So each row seems to be a ramp (start, end, delta) and three settings.

Here's how you could replace all your FOR loops (each also had a 100ms wait!) with a tiny stack with the following advantages.

• The code will work no matter how many rows exists (scalability!)
• You still need to decide what to do with rows that are incomplete or should be skipped
• There are many fewer places for bugs to hide. (e.g. that birds nest of wired indices is difficult to check for correctness and miswiring is a clear possibility!)
• Much less duplicate code! (For example how many times do you think you need to initialize the same empty array in parallel? Once should be enough!)

This is the way to go unless you get paid based on the size of the diagram!

[altenbach]

Here's how your entire code could look like!

Fits on  postcard instead of a wall poster! 😄

[Falc0n]

Oh, thank you for the advice! I’m not a professional and don’t have enough experience to understand how you did it so easily. I usually rely on trial and error.

[Falc0n]

and if you already did it, can U share .vi with me?