There's a pattern that I've seen a couple places - MS Access being the
one that comes immediately to mind - where a person is doing
row-oriented data entry and filling in one row then hitting return
causes a new empty row to be created automatically so the person can
continue data entry without hav
The table interaction in MS Word is,
- Tab to the next cell in a row
- In the last (right most) cell of a row, tab wraps down.
- If no row on wrap, create a new one.
- Enter puts a line break in the current cell contents.
MS Excel goes down a row on Enter.
Applications like Work have the need to
I think it would be more efficient to create a new row, once a character is
typed in the last empty row. The newly created row is not deleted, if all
the characters are cleared in the row above it. The second empty row
is removed, whenever the screen is refreshed. Copy and paste would create as
man
That is a good point Oleh. I've used that approach before in a query
editor UI, and have seen it often before - there is always a blank
row to go to at the bottom of the list. As soon as any focus is given
to that last row, a new one comes in below it. If one were to close
out of the interface at t
Google Profiles has an _excellent_ example of creating new input fields on
the fly as you're interacting with the first available one. Check it out;
create a Google Profile and pay special attention while adding something
under "Places I've lived", "Companies I've worked for", or "Schools I've
atte
