Why would VI's with my XControl want to be saved when opened?

[Ben]

This is just a general question about XControls.

What could I be doing wrong in my XControl that would make any VI that uses the XControl want to be saved when I open it. THe "Explain Changes" dialogs says that there were "cosmetic changes".

Does anyone have any ideas off hand?

Ben

[TCPlomp]

Hi Ben,

most likely this always happens once you set the 'State Changed?' or 'Data Changed?' to true.

Ton

[altenbach]

b..b....b....b..but why?

[Ben]

I am changing the "State" cluster in the init code. Not setting the boolean anywhere except the "Panel re-size" event of teh Facade. I would not think the pnael re-size event is firing unless I am re-sizing the control.

If i stumble across the cause I'll post back.

Ben

[Ben]

I was hesitant to post the XControl but I am only limiting the community's ability to help and learn.

Here is the project in LV 8.2.1.

This XControl is intended to be a color ramp that can be used to illustrate gradiants in a system. I am using it to illustrate the temp change across heaters and heat exchangers.

Please keep in mind that this is my first attempt at developing an XControl from scratch. I also do not concider this a finished XControl since I have not added mtethods to define the color ramp yet.

If you have any ideas, fire away!

Otherwise I hope it helps someone!

Ben

Message Edited by Ben on 01-09-2008 12:13 PM

Message Edited by Ben on 01-09-2008 12:14 PM

[Ben]

Re: The above example and XControls and non-visable FP's under LV 8.2.1

I found out yesterday that the image of an XControl will not update if the FP is not visable. THis appears to have been fixed in LV 8.5.

Still haven't figured out the save thing yet.

Ben

[MeghanK]

Hi Ben,

I opened up your color ramp VIs and I could not get the save dialog to display upon opening.  I also used your xcontrol in different VIs, and I still could not produce the dialog.  I used LabVIEW 8.2.1 and LabVIEW 8.5.  Please let me know how I can reproduce this issue, thanks!

[Ben]

Meghan wrote "I could not get the save dialog to display upon opening. "

No, not a save dialog on open.

When you open the VI there is an asterisk next to the name in the title bar.

Are you telling me you did not get the asterisk?

I just had another engineer try it on his machine and he got the asterisk.

Even after he saved it and closed it, on re-open he got the asterisk.

Ben

[Ben]

See image for the asterisk.

Ben

Message Edited by Ben on 01-11-2008 09:58 AM

[Bob Schneider]

I'm having the same troubles with a colormap in a project of mine.  I had done original development in 8.2.1, and after upgrading to 8.5, I experienced the wanting to save the VI for "cosmetic changes" every single time I opened the VI, regardless if I actually changed anything.  After I read this thread I thought, hey maybe it's the color map.  So I removed it, and the desire to save cosmetic changes disappeared.  Then, I tried placing a new colormap into the VI... the cosmetic changes reappeared.

I even then went as far as simply creating a new VI, dropping a color map, and then saving the VI to my desktop.  I then opened it, and it wanted to save changes again for "cosmetic reasons."

-Bob