3 réponses à ce sujet

[Kesaru]

Okay, I'm pretty sure this has to have been detailed somewhere, but somehow I couldn't find anything on it.
What do I do to reopen an altered version of an existing script I've created? Once you close the toolset the base scripts you altered no longer have the changes you made, so you can't just select it in the toolset unless you made an entirely new script.
The scripts were exported, which I assume is necessary. I just can't figure out how to open them in the toolset.

Modifié par Kesaru, 13 mars 2010 - 05:53 .

[TimelordDC]

If you are working with core scripts, you need to check them out for your changes to persist. Otherwise, you can open only a read-only copy (title has red background) or a local copy which cannot be saved (title has yellow background).

If its a new script you've created, it will be under whichever folder you created it under with the default checked-out status (meaning, it is editable and changes can be saved)

[Craig Graff]

If you want to preserve a history of your changes or keep separate versions that you switch between, I recommend checking out each resource before making a change and then checking it in once the change is complete. To access the history, right-click the resource (either in the palette window or the resource tab at the top of the toolset) and select resource history. There is a bug that the resource history won't immediately populate the first time it's opened during a toolset session, so you will have to click on the resource again to see the history. You can then right click on any version in the resource history to restore it.



In your case, you should be able to open up the .nss files in your override directory (they are plain text files), you can then copy the contents into the script after you have checked it out.

[Kesaru]

Thank you, you both helped a lot.