Renaming typedef file caused constants reset

Question

Hello!
Here's a short description of the problem I encountered:
I renamed the filename of the typedef that was used in my state machine for state coding (see for example State Machine template shipped with LV). As result I lost values of ALL constants that coded states in my state machine, i.e. they were reset to value of the first value in state enum.
Note: when opening state machine that used the typedef
I got the message something like "VI was changed in memory. Reload from disk or view from the memory?". And 2 buttons: View and Discard. I clicked "View".
Then after restoring all constants manually, I saved my work to archive and tried to rename typedef file again, the result was the same - all constants reset to first value of enum.
I restored files from archive, again renamed typedef file,
then closed my app WITHOUT saving state machine that used typedef. After opening my program I got the message "Searching for my typedef", pressed "Browse..." and loaded typedef from renamed file. Constants were left without any change (uh-r-r-a!).
Before posting this message to forum I tried to make an example to show the problem, but o-o-ps I failed to do it.
It didn't repeat even with my program.
This post can't be considered as bug report, as I can't repeat the problem. But I think the problem exists as I lost values of all constants after renaming typedef file, and this is the fact.
So my advice (that old as the world) to everybody is to save work even when innocent actions are made such as renaming typedef file names.
Probably somebody encountered this problem and knows how to repeat it.
Thanks for attention.
Any comments appreciated.
Rashid.
Using LV 8.0 (LV Run Time Engine 8.0.1) on Win XP with Russian locale, all VIs used in my programs have names in cyrillic sometimes mixed with english letters, e.g. "russian name (typedef).ctl".

Answer 1

Hello, Charlie,
I can say absolutely sure that I always used LabView to rename my typedef file. I never use Windows Explorer to rename typedef files (or any other LV files) in my practice.
Besides, when the values of my constants were reset there wasn't any broken wires. The block diagram wasn't corrupted. Everything was fine except default values of my constants. Due to that I noticed this error a little later - after renaming typedef file I ran my program and couldn't understand why it fails to act as should. When debugging this problem I went down to my state machine and only then I saw that all my state constants are reset to default values.
I never used "Substitute copy for original". I used only
"Rename" when renaming my typedef file.
I didn't add any items to my typedef. The only things I did are:
- renaming my typedef enum label in the *.ctl file;
- and "Save as.." -> "Rename..." - renaming my typedef file.
Besides, when I did try renaming 2nd time to reproduce such behaviour: I left typedef enum label without change and the behaviour was the same.
So, such behaviour (loosing constant values) I get TWO times.
But after I worked around this (see 1st post) I couldn't already reproduce this behaviour.
If I'll succeed in this one more time again, and be able to reproduce this behaviour, I'll certainly post to you my steps.
Thanks for attention.
Rashid.
P.S.
1. As to broken wires if I get it right - in your case you added new items to typedef but your case structure in state machine was not updated to contain new states handlers. If so, then it's obvious why you got broken wires. But as I didn't change the typedef itself (only renamed it), I didn't get broken wires.
2. I wouldn't be surprised if I'd have done something in the weird way: I mean renaming by Explorer or saving, closing and so on. I was doing everything from the LabView environment. As far as I remember I didn't rename the state machine vi file at that, only typedef file. And my state machine was always opened. The only file I was opening/renaming/closing was typedef file. And as far as I remember I opened it by "File -> Open..." and not right-clicking at constant and "Open TypeDef..".
3. I understand that my description is foggy :-) and that it's difficult to find this weird set of steps, but who knows. Anyway I appreciate your help.Message Edited by Rashid on 06-13-2006 12:03 PM