https://bugs.freedesktop.org/show_bug.cgi?id=54067

Lionel Elie Mamane <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
                 CC|                            |[email protected]
     Ever Confirmed|0                           |1
            Summary|UI: Silent FILESAVE         |UI: Base FILESAVE semantics
                   |although user wants to      |confusing & inconsistent
                   |discard                     |

--- Comment #1 from Lionel Elie Mamane <[email protected]> 2012-08-27 06:53:44 
UTC ---
"Implicit" immediate save of data without an explicit separate save operation
is the usual in database environment. If we would not save changes to data
implicitly, then embedded databases would behave differently from external
databases, leading to user confusion.

So, the current situation, in theory, is:

 1) Change to data itself => implicit save
 2) Change to query/report/form/... => explicit save

What I expect would be weird for users is that changes of category 2 actually
need to be saved *twice*:

 1) Once in the form/report/... window, which saves them in the in-memory
archive structure.
 2) Then go to the main database window, and click "save" there. This commits
the in-memory archive structure to disk.

Also, I can easily imagine (not tested yet) that if one makes a change to a
form, saves it *only* in the first sense above, and then a data change, then
the whole archive structure is saved, including the form change. To me these
semantics start to feel baroque. To say the least, this also leads to user
confusion.


Just to be even more confused, changes to Basic code *used* to follow the
"two-step save" semantics in older versions, but now saving from within the
Basic code window *also* commits the odb to disk (it does a "save in the main
window").


What I propose is to eliminate the second save everywhere: when one clicks on
"save" in a report or form, also commit to disk. In this way, data follows its
usual "implicit save" semantics *and* when the user saves something (in Basic /
Form / Report / ... window), it is actually saved.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to