View Full Version : Wrong ccf loading
Poorman65
September 19th, 2007, 08:40 PM
I have had this happen to me quite a bit and it has burned me a few times because I didn't notice that I was updating the wrong ccf.
I am in the habit of saving different versions of my CCF to avoid having one get corrupted and wiping out my work (which has happened). I
name them like this:
MyThing1.ccf
MyThing2.ccf
MyThing3.ccf
... and so on
To recreate the problem do the following:
1) Open Designer to whatever it defaults to such as MyThing1.ccf
2) Close MyThing1.ccf
3) Open MyThing3.ccf
4) Close Designer
5) Open Designer and it loads MyThing1.ccf
This really should re-open the last one that I was editing which is MyThing3.ccf, but it doesn't.
(Note that this problem still occurs with the new 100 PRE build)
tmorten
September 19th, 2007, 09:03 PM
I believe Designer loads whatever the last CCF loaded into NetRemote was (as opposed to the last CCF edited)... let me know if that's the behavior you observe on your end as well.
Best,
Tim
Poorman65
September 19th, 2007, 09:31 PM
That is not the behavior that I am seeing. I just verified it. (It seems incorrect anyway, but in most cases they are the same).
Rob H
September 20th, 2007, 12:59 AM
I'm a bit confused, can you clarify what you are seeing?
When you say :-
1) Open Designer to whatever it defaults to such as MyThing1.ccf
2) Close MyThing1.ccf
3) Open MyThing3.ccf
4) Close Designer
5) Open Designer and it loads MyThing1.ccf
Can you confirm that you are closing and opening in NRD.
In which case the last CCF that you actually opened directly in NR would be MyThing1.ccf?
Poorman65
September 21st, 2007, 02:30 PM
After the suggestion that the latest CCF from NetRemote would be the one loaded in the designer I did the following;
1) Open NRD
2) Close MyThing1.ccf
3) Open MyThing2.ccf
4) Send ccf to NR
5) Close NRD
6) Close NR (I think this was done as well)
7) Restart NRD
NRD opened MyThing1.ccf
I will step through this scenario again and make sure that I am explaining the steps accurately.
tmorten
September 21st, 2007, 02:59 PM
Instead of sending from NetRemote Designer, try opening with NetRemote from the File | Load | Interface File (CCF)... I think that is where the registry key gets set which determines the file that will be loaded when next you launch NetRemote.
Best,
Tim
Rob H
September 21st, 2007, 04:13 PM
Yes, that's my understanding too Tim
Poorman65
September 22nd, 2007, 12:16 PM
It does seem to work the way you are describing now, but that is a bit non-intuitive. The common way for this to be done is that the Editing tool remembers what document(s) it had open during the last editing session. In this case, you have the test tool remembering. I don't think that a user would expect this behavior and it can mess up their applications.
In my case I ended up working with an older version of my CCF that was missing some important work that I had added. By the time I realized I had a problem, I had overwritten the new stuff.
Also, I end up having to restart NRD quite often when I am working with Girder because their is no way to refresh the Girder instance in the NRD Action editing. The only way to get them updated is to restart NRD.
This is not a devastating problem, but it is irritating. Thanks for clarifying this and I hope that you decide to change the behavior. Also, an automatic backup mechanism would eliminate the need for me to work in the manner that I currently have to. I lost a bunch of work because my CCF was corrupted. That is why have been doing the versioning so regularly.
tmorten
September 22nd, 2007, 02:48 PM
Thanks for the feedback; good points all. I'll add these to the wishlist.
Best,
Tim
Powered by vBulletin® Version 4.1.8 Copyright © 2012 vBulletin Solutions, Inc. All rights reserved.