You sent me a private message indicating you still don’t understand, including a long article describing the differences between save and save as which completely misses the problems I experienced. So, I’m going to try and give you an example of how your system is NOT typical.
Here is a typical system where I am editing a document called happiness.
Notice the name of the file. Now, I edit the document and do a save as using the name sadness. Look what happens.
This is what the standard practice is. This is what all programs I’ve ever seen do, except for emClient. When you save as another name, the user is moved into the document with the other name, as Libre office (or word for that matter), moved me from the document happiness to the document sadness.
In Word or any other program, when I return to the document I edited and saved, it has what I edited and saved.
There is nothing wrong with deciding people should not be able to edit the themes. The problem is that when I edit a file, theme or configuration, or registry or whatever, and save and then see that the file is now how I like it, and then exit the program after saving, I don’t expect to come back to the file and have it lose all my edits.
Your process for editing settings is entirely different from your process for editing themes. It was not clear to me that I was now in another file, and not in the themes file I was editing.
I made a few suggestions for making this process clearer to the user. Do you believe those are all worthless? Can you improve on them?
Are you saying that those of us who had problems not following your user interface are just idiots and there is no way emclient could make the process clearer?