Ctl reedited is invalid after saved

[Vandy_Gan]

Hi everyone,

there was a code's picture that reedit ctl‘s Booltext and saved to new file, it workd ok in development environment，but new ctl could be invalid when it run as exe at runtime ,I did not how to solute it.Could you give me some suggestion.

Thank you.

[ensegre]

I do not know what is a LV stringApp instance, but I doubt that it is exactly a loadable control. What are you trying to achieve exactly?

[Vandy_Gan]

42 minutes ago, ensegre said:

I do not know what is a LV stringApp instance, but I doubt that it is exactly a loadable control. What are you trying to achieve exactly?

 

ensegre, thank you for your reply, I want to achieve one application(exe) that has the function: edit a template boolean ctl's BoolText and save to new boolean ctl by programming. And the code works fine in development environment, but it is invaild at runtime when used the exe built.

[ensegre]

I would have said why don't you use Save.Instrument which is a public method, but I see that it is not supported in runtime, and that is stated expressly. A fortiori, a private method which "must wait until the user interface isidle" might be a completely IDE thing.

[Zou]

It's just boolean text.  Do you really need to save it a file?

[Vandy_Gan]

@Zou Also I would modify text's property ,e.g. font ,size , position .Becuase I would like to achieve to modify batch more ctrls 

[Vandy_Gan]

14 hours ago, ensegre said:

I would have said why don't you use Save.Instrument which is a public method, but I see that it is not supported in runtime, and that is stated expressly. A fortiori, a private method which "must wait until the user interface isidle" might be a completely IDE thing.

@ensegreI had watch a video that demonstrate the function on the YouTube, but I did not remember the link of it

[Rolf Kalbermatter]

Many functions in LabVIEW that are related to editing VIs are restricted to only run in the editor runtime. That generally also involves almost all VI Server functions that modify things of LabVIEW objects except UI things (so the editing of your UI boolean text is safe) but the saving of such a control is not supported.

And all the brown nodes are anyways private, this means they may work, or not, or stop working, or get removed in a future version of LabVIEW at NI's whole discretion. Use of them is fun in your trials and exercises but a no-go in any end user application unless you want to risk breaking your app for several possible reasons, such as building an executable of it, upgrading the LabVIEW version, or simply bad luck.

Edited 4 hours ago by Rolf Kalbermatter

[ensegre]

17 hours ago, Vandy_Gan said:

@Zou Also I would modify text's property ,e.g. font ,size , position .Becuase I would like to achieve to modify batch more ctrls 

And must you really do it in a compiled executable? Cosmetic properties you can change programmatically on the fly even in an exe.