[Gnumed-devel] Encounter editing (where saving changes is not currently the default)

[Jim Busser]

First of all, there is a failure to refresh the Encounters list after one of 
its items can be edited. Should I log that somewhere or is it directly enough 
able to be taken care of?

Also, can I request a change to the default button within encounter list item 
editing? Presently, on editing from the list of encounters, saving one's 
changes is not the default.

If that is intentional, could I give a counter-argument?

I would think that --  normally -- a user would only be altering values 
intentionally. An exception may apply when a user was able to jump past a 
(perhaps never-yet coded) read-only level, into some deeper level where the 
"read" is only offered as part of a "write" and stray keystrokes could 
unintendly change a value. In that scenario yes, it might make sense to lose 
the changes if the user did not explicitly click a Save button.

In this case however, the user only got to this window by clicking or 
keyboard-shortcutting the Edit button.

I suggest that where a serious (especially irreversible) action is going to be 
committed, it would be better handled with a *confirmation*, instead of making 
the default to do nothing and lose the value of what had been inputted?

-- Jim