07-22-2021, 08:34 PM
(07-22-2021, 06:49 PM)remkonoteboom Wrote: The difference between something like TACTIC and Google Sheets, etc is that data changes have little to no repercussions. For example, if I misspell a word in a Google doc or change a number in a spreadsheet, the worst that can happen is somebody sees that mistake as I quickly correct it.
However, if someone completes a task in TACTIC, it could spawn a render and who knows what else, depending on how a workflow is defined. So someone switching things back and forth could have can large consequences downstream. The way applications usually handle significant changes is by opening an "Are you sure?" popup. However, this is impractical on a spreadsheet like interface.
Or they have an edit form which popups and those always have a save button.
The save button provides a safety net. An action that force the user to think about the consequences of their actions by reviewing their changes. So if the save button is removed, we need to have a way where users cannot make little mistakes with drastic consequences.
Yes that's what I was trying to say when I was referring to the triggers problem.
Anyway rigging an "auto save" behavior to be called in place of spt.table.set_changed_color shouldn't be to difficult, we could set it with a kwarg auto_save for TableLayoutWdg, defaults to false and can be activated for views where it is wanted
