An issue with the Archive feature eventually led to a workflow question; namely, that it's possible to archive source that has been modified in-editor but not saved, later potentially resulting in a repository commit that doesn't match the archive.
To give options to prevent this, two new options in preferences have been proposed:
"autosave on build" (or "autosave on compile" because we don't use the "build" nomenclature in Propeller Tool)
(mutually-exclusive with #1) "warn on archive if modifications unsaved."
[ ] This is settable/clearable only if #1 is unselected; otherwise it's grayed-out and ignored during archiving.
1, when selected, will automatically save any opened and modified source that is successfully compiled into the application.
2, when selected (and if #1 is unselected), will prompt the user if any of the opened and modified source is unsaved. At the very least, this gives the user the ability to willfully abort archiving upon such knowledge.
An issue with the Archive feature eventually led to a workflow question; namely, that it's possible to archive source that has been modified in-editor but not saved, later potentially resulting in a repository commit that doesn't match the archive.
To give options to prevent this, two new options in preferences have been proposed:
1, when selected, will automatically save any opened and modified source that is successfully compiled into the application.
2, when selected (and if #1 is unselected), will prompt the user if any of the opened and modified source is unsaved. At the very least, this gives the user the ability to willfully abort archiving upon such knowledge.