Re: [PyCAM-devel] Persistence of project settings?

[Reuben R. <si...@em...>]

>> I can imagine the following approaches.  Please share your opinions, which of
>> these approaches you would prefer as the default behaviour of PyCAM.
>>
>> A) always load hard-coded initial project settings; do not store any changes
>>     (this was pycam's behaviour up to now)
>> B) load project settings from a file at startup and store the final state of
>>     the projects settings into the same file when exiting (without confirmation)
>> C) same as (B) - but ask for confirmation
>> D) same as (B) - but store changes continuously (more crash-safe)
>   
> Based on the lack of responses, I assume that the topic was either not well
> explained by me or you simply do not deem it to be really important.
> Feel free to complain, if it was the former :)
For myself, I barely have used Pycam. To reply to this subject might 
have shown my inexperience.
>
> Now I picked the approach based on my own habits, which are reflected by
> option (C) from above.  Thus settings will be handled like this:
> - always load the project settings from the same file
> - ask on exit if changes should be saved to that file
>    (optional: "remember this choice forever")
>
> This allows pycam to be usable with a persistent session state (tools,
> processes, ...) if the user confirms this behaviour.
This is what I would have picked for myself.
>
> Cheers,
> Lars