Aller au contenu

Photo

How to save properly when handling campaign module?


  • Veuillez vous connecter pour répondre
6 réponses à ce sujet

#1
JackFuzz

JackFuzz
  • Members
  • 408 messages
I "checked out" a conversation file from the core campaign files.

I did my work.

I saved the file.

I exported properly.

Now do I check it back in?  Won't that make my changes permanent? I'd still like to have a copy of the work I did and a copy of the original campaign file.

Is there a part in the tutorial somewhere that shows us how to save properly?

UPDATE:

Just use the resource history and revert back to the 2nd one if you ever need to.

Modifié par JackFuzz, 24 décembre 2009 - 02:05 .


#2
SilentCid

SilentCid
  • Members
  • 338 messages
The check-in feature doesn't make anything permanent, it just makes it from a writable resource file to a read-only resource file. The toolset was originally part of BioWare's collaboration software. When a resource is checked out by someone, it insures that another person in the office can't edit the file while that person is working on it. Once that person is done with his work he would select check-in and give notes on the changes when he was working on the file.



Since the collaboration part doesn't really apply outside of BioWare. You don't really need to check it in each and everytime if you want to save. Just go to the top of the toolbar and hit save as if you are saving a document.

#3
JackFuzz

JackFuzz
  • Members
  • 408 messages

SilentCid wrote...

The check-in feature doesn't make anything permanent, it just makes it from a writable resource file to a read-only resource file. The toolset was originally part of BioWare's collaboration software. When a resource is checked out by someone, it insures that another person in the office can't edit the file while that person is working on it. Once that person is done with his work he would select check-in and give notes on the changes when he was working on the file.

Since the collaboration part doesn't really apply outside of BioWare. You don't really need to check it in each and everytime if you want to save. Just go to the top of the toolbar and hit save as if you are saving a document.


Well in order to edit it, you have to check it out.  Once you've saved it that means letting the file stay checked out. 

Is that how it's supposed to work? I thought you always want to check stuff in when you're done with it?

You can use the resource history to revert back to the original (which is the 2nd in the slot I think).

What do you think?

#4
Avaraen

Avaraen
  • Members
  • 342 messages
There's no need to check the file in locally, because you don't have the file shared with anyone. I sometimes use the check-in feature if I want to experiment and preserve earlier changes, but otherwise, it really isn't necessary.

#5
FalloutBoy

FalloutBoy
  • Members
  • 580 messages
Check it in if you want to, or don't if you don't. I generally only check in things that I am pretty confident that I won't be changing any time soon and I want to prevent any accidental breakage. Which isn't very much at this point, but I'm sure there will be more as I go along.

#6
JackFuzz

JackFuzz
  • Members
  • 408 messages
Another thing guys. Let's say you check out a file and make two changes.  Note those two changes when you check it back in.

You'll have an organized history of changes you made.

Always check in & check out.  If you make a mistake you can revert back to a point in resource history where things worked properly without losing much work.

#7
Avaraen

Avaraen
  • Members
  • 342 messages
Part of the reason I *don't* check-in every time I make a couple minor changes, is because I haven't seen any way to revert back to Bioware's original file once my changes are checked-in. I keep a log of changes I make in a .txt file (also used for the release readme).