My proposition is to separate the current settings for a print (i.e. a process), from template settings. Let me explain: the current way the profile is handled is, that as one changes a setting in the process, one changes in fact the profile (indicated by "(modified)"). When we eventually change the profile, we are asked, if we want to save the changes, and that is rather irritating, since even switching on and off support generation will "modify" the profile in memory. Wouldn't it be better if there was a profile, with all the filament and quality settings which serves as an initial template for a new process, and to keep the actual settings a property of the process (leaving the template untouched).
I'm not sure, if I make myself clear, so maybe an example is helpful: think about Word for instance, if you want to write a letter, you will most likely create a new document based on a template (like letter.dot or any other). When you change the size of the font, you change it for the document you're working on, but you leave the template untouched. But if you need to change the template, of course you can by editing the dot-file. In my eyes, if S3D handled settings that way, there would be at least a little less reason for frustration. Especially, since it is not obvious, which setting has been changed (the GUI does not give a clue), it can be irritating: should I save the modified settings to the profile or not? And what happens for example if I use more than one instance of S3D on my PC, and I change something in one and something else in another instance: I may save in one instance, then in the other and loose of course all the changes made and saved previously... And the factory files contain a profile, which can be totally different from the current profile and if you click update by mistake, you will probably utter some sware words as soon as you realize the result. See what I mean?
So for S3D I imagine the following:
-manage the settings in a template (currently called a profile): could be done basically in the same way it is done now for a process
-apply any stored template at any time to a process (resetting all potential previous changes)
-allow the current settings to be stored as a (new) template
-de luxe would be if the GUI indicated, which settings are different from the template
Thank you very much for considering!
