In modal dialogs, committing a change to a cell and
committing a change to the model represented by the table are, or should be, two
separate things. But in any circumstance, you are assuming the user knows of
this "affirmative commit" requirement. Really? What is it? Does Enter do
it? Just one of the Enters or either? How about Tab? Pressing the Ok button?
Pressing the Next button? Pressing the Finish button? Clicking in another field?
If a user enters a value in one column then clicks in another, should the first
value revert? I'll stick to my contention that this behavior violates user
expectations and is just a bug.
I know from experience that if a developer leaves
this behavior in an application, bug reports will be filed and the developer
will have to fix it.
Bob
Object Factory Inc.
----- Original Message -----
Sent: Monday, April 01, 2002 10:13
AM
Subject: Re: [platform-ui-dev] Question
on implementing CellEditor manager
The only case I think of off
hand is that it makes committing less controllable. For example when one is
editing a text cell editor and wants to go and copy some text to paste in
before committing the change.
Same problem in Swing. A well-known bug that every developer has to
fix. I'd like to see JFace handle this generically.
Bob Object
Factory Inc.
Randy Hudson <hudsonr@xxxxxxxxxx> wrote: > I
expect Randy Giffen can answer this one.. > > Is there a technical
reason why CellEditors aren't committed when they lost > focus?
I am managing some CellEditors now, and there are
several different > events that can happen in which I will either
cancel or commit the cell > editor. Right now I am committing on
focus lost (if
dirty).
_______________________________________________ platform-ui-dev
mailing
list platform-ui-dev@xxxxxxxxxxx http://dev.eclipse.org/mailman/listinfo/platform-ui-dev
|