Xcontrol asked to save in the execution !

[brightest]

Hi !

I have used some Xcontrol in a project and my program work well in development system but ...

I have made executable file and when it is running and I want to Exit from this (using Exit labview function ) ,

SAVE CHANGES window opens and want to save data changes in " Data.ctl " and " State.ctl " files of all Xcontrols !

Why it happend and how can I do to fix it ?

Thanks and sorry for my broaken English . 

[Wiebe@CARYA]

What version of LabVIEW are you using? Many XControls problems in 8.0 where resolved in 8.2.1.

Regards,

Wiebe.

[brightest]

Hi !

I use 8.2.1 version with DSC Module 8.2.1 .

I got another problem with Xcontrol.

I want to bind an Xcontrol including some Control and Indicators to a shared variable that I have defined it's type to Data.ctl control of my Xcontrol .

I want when the value of control inside of an Xcontrol changes then the value of a same control of a same another  Xcontrol that is binded to same shared variable changes so.

What can I do for this ?

I have tried some ways but there is no result !

Thanks very much

[TCPlomp]

What code do you have in your "Unint" ability?

Ton

[brightest]

It is optional and i have not used of uninit.vi ability .I searched ni.com for more information about "convert state for save" and "uninit "abilities but I found nothing about them.How can I use of them ?

Thanks for your answers

[brightest]

The code is not important becuase I tried it with a new xcontrol without any changes and got same results.

Message Edited by brightest on 08-22-2007 06:35 PM

[TCPlomp]

Maybe an idea.
Use a master typedef, let the data ability of the XControl contain that master typedef and have the Shared variable contain that master typedef.

I know the data ability stores some special things that are not really related inside it's ctl.

Ton

[AdnanZ]

Hi brightest,

I hope you are doing well today! I tried to build an executable on my own machine with a very basic project which uses a XControl and did not see any problems when closing the executable. Is it possible for you to post a stripped down version of your code which highlights the issues you are facing? Include both the executable issue and the shared variable issue. I am asking for your code so as to see what exact steps you have taken to create and run your executable as well as how you have bound to the shared variable. As mentioned above, we released XControls with LabVIEW 8.0. Any feedback and help on this feature is greatly appreciated!

Uninit Ability:
This is an optional ability and is used to release any resources that you have allocated for the XControl. Typically such resources are allocated in the Init VI, although they can also be allocated in the Facade. Open resource references should be stored in the State so that the Init, Facade, and Uninit VIs can access them.


Convert State for Save Ability:
Also an optional ability and is used to modify the state information that LabVIEW stores with a VI. The most common use case is to remove non-persistent data, such as references, from the state. Removing non-persistent data reduces the disk footprint of VIs using the XControl.
Because most modern computers have large storage disks, reducing the disk footprint does not often justify the additional programming effort and processor time required to remove non-persistent items. You should primarily use Convert State for Save to remove large arrays of non-persistent data. Reducing the disk footprint may be important for applications which are targeted to non-desktop targets; however, these targets rarely implement complex user interfaces which would benefit from XControls.
To convert the state before saving, save a copy of the state cluster and remove any non-persistent items. Use the Cluster functions to convert the full state cluster to the save state cluster, and then wire the save cluster into the variant output. Type define the save state cluster, because you also need to use it in the Init ability.
When you use the Convert State for Save ability you must also modify the Init ability to convert the Save State back to the full state. Failing to properly convert the state results in an error in the Variant to Data function, which causes the Init VI to use the default state values, thus losing any saved information. Use the same Save State type definition you used in the Uninit ability to convert the variant to a cluster. Use the cluster to set persistent information in the full state, and then initialize non-persistent items normally.

[brightest]

Thank you Adnan Z for your answer

I'm so sorry because I have been so busy today and had not enough time for working on it and just now , I must go somewhere in out of my city for 3 days,anyway.

I send a code here after my come back but I don't think that It could be usefull .

I created an empty Xcontrol without any changes on it and got that problem .

Could be my problem for the application builder settings ?  what do you think about it ?

Can you send that your simple tested project or it's setting here ?

Best regards and thanks again

[AdnanZ]

I am not sure if its your application builder settings. Post the stripped down version of your code; and we should be able to debug it better. Here is the basic code I created.