xEdit and file saving - other ways to do it?

[Erundil]

Currently, when I save a file in xEdit, it doesn't really get saved. The program creates a separate file and "queues it" to replace the original file when xEdit is being closed.

 

It's far from optimal. First, because it's a unique behavior, unlike any other file editor in popular use. If you save the file, it saves the file! Why is xEdit a special snowflake? There must have been a reason behind this choice, but it's still a weird choice. The problem becomes apparent when I save the file and - say - electricity goes out. Happens a lot in my area lately.

The program didn't close "peacefully", it was forcefully shut down by the lack of power. But, I saved the file, so it's saved, right?

Nope, gotta manually find a backup somewhere, rename it, replace the original file... A lot of hassle.

 

What I'm looking for is a switch in the settings (or a launch paramater, doesn't matter), that would disable the save queue functionality. That would make xEdit actually save the file, when I press Ctrl+S, just like every other normal program does.

 

Any help would be appreciated.

 

[Greg]

https://wiki.step-project.com/Guide:XEdit#Save_and_Exit

 

The STEP guide indicates you can use Ctrl+S to force saving changes at any time without exiting, but the changes are saved to a backup file instead of to the plugin directly. If you need to continue editing after losing power with the last saved file, you''ll need to move the last backup file over the main plugin before running xEdit.

 

https://tes5edit.github.io/docs/8-managing-mod-files.html

 

The TES5Edit guide states you can use Alt+S or close xEdit to save the changes, but it sounds as if Alt+S may be a shortcut to close (or close and save) xEdit.