Start a new topic

Autosave function

Hi all!

We have been avid users of RoyalsTS since a long time. The feature mostly missed and the one I have nagged a bit about before is a Autosave feature so you can choose if you want RoyalTS to do a save every X timeslice.

So may times someone has forgotten to save after having added and done changes just to have a PC crash, RoyalTS crash, och similar...

This is highly annoying and as it is, I might start looking at the competition, I really like RoyalTS, but this is highly annoying and I feel it should not be that a difficult function to implement...

Please look to add this, if RoyalTS did and optional autosave every 15 mins so whatever would be super!

Merry christmas and happy new years!


1 person likes this idea

Hi Dave,

auto save on a time basis is hard to implement because of all the cross threading and concurrency issues. We did implement a feature in V4 which may do the same job:

"Save Document after using the Properties dialog"

See also:

Let me know if this helps.


2 people like this

Hi Stefan, I looked for this option but I can not seem to find it. Please can you provide with steps of how I turn it on?

Sorry if this is a basic question.

Kind Regards,

Darren Gipson

Hi Darren,

in the Navigation panel, right-click on the document you want to enable this feature and open the properties. There you will find the setting on the first page. Make sure you are using the latest version of Royal TS.

Let me know if this helps.


Ah, that would explain it. I was trying to enable it on the Application itself. Is this possible? I store all of my credentials at the Application level.

The application "document" is saved automatically when Royal TS is closed. If you want to have more control over that, I recommend to move the creds to a dedicated document.


Thanks for your quick responses Stefan. We use a team document so I can not stored the credentials in the document. 

My use case is this:

I created a new credential in the application document. I forgot to save and my machine got rebooted. So I lost the user/password combination.

I realise that it is my own downful and I should have saved.

Hi Darren,

unless you aren't using the free Shareware edition of Royal TS, you can create and load multiple documents at once. So you should be able to load your personal credential file next to your team document.


Just to add my piece to this thread, in the current version of RoyalTS, shared documents are working pretty well in my team.

However, we've discovered an issue around saving.

If PersonA in the team is modifying an object in a document (ie has the Properties window open for that object), and PersonB (unbeknownst to PersonA) is also modifying the same object from the same document, the following happens.  PersonA finishes, and exits the object Properties window.  Then PersonB also finishes modifying the object and closes the Properties window.  PersonA saves their document.  Sometime after, PersonB saves their document.  After clicking the merge button (that shows up in bottom right corner of RoyalTS, PersonA now takes a look at the object, and anything they did was overwritten by PersonB's modifications.  Even if PersonB didn't touch the particular field that PersonA was modifying.

Even with the option "Save Document after using the Properties dialog" ticked, it still doesn't address the different times in saving. 

Hi Neil,

thanks for sharing your issue. Unfortunately this is "by design". If a user clicks on OK in the properties dialog, the object will be marked as "modified" - even if it hasn't been modified. This is because of the datastructure we use internally. Not sure if I should go into all the details but it's related to how Royal TS determines which properties should be written (we do not write values which are "default" values for efficiency). So there's a chance that even though the user didn't change the value, it might change the object because of a changed default value and there's no other way to ensure the new value will be written to disk. In this case, the user who clicked OK last will win in the merge scenario.


Login or Signup to post a comment