[lmi] Direct drill-down census editor testing

[Wendy Boutin]

I've done some preliminary testing with the new census editor and
would like to share my feedback. I broke it down into a few different
categories.

Navigation:

1. Keyboard navigation is very limited. I can use the up and down
arrow keys to select different cells, but I can't drill down to
any particular data column within a cell. It would seem normal
to use the tab key between columns. The tab key doesn't work too
well in the 'InputSequenceEntry' controls either.

2. It's natural for most users to double-click the field they want
to modify, but that doesn't seem to work like I'd expect. The census
editor seems more like two single-clicks instead.

3. Right-clicking in the census view behaves differently, but I
think it's an improvement. Now, right-clicking is only allowed
when a particular cell is selected and at no other time. Previously,
the behavior could be seen as confusing. I'm not positive it
was completely wrong, but here's an example:

  File | New | Census | Add a few cells and a distinction among them
  focus on any cell besides the first
  move the mouse away from the cell grid, then right-click
  pick 'Edit cell'

The dialog that opens has the first cell's data instead of the
one that appears in focus. The new behavior is better because
it only allows the right-click menu when used within the census
grid. And, even better, is the intended cell's data is actually
selected.

Cosmetic:

4. The size of input controls is inconsistent; text controls look
shorter in height than all other controls. Also, within the text
control, the alignment of the inputted text makes it difficult to
read. Maybe all it needs is a border, but right now it isn't easy
to distinguish a 'q', 'g', and 'p'.

5. Selecting a control for editing causes it to grow tall enough
to cover much of the data in the row below it. It can be convenient
to see the next cells data if a user is editing an entire column
from top to bottom.

Input validation:

6. There isn't any input validation in the census view. It really
needs to have the same level of input validation that's currently
in the individual cell input screens. For example, 'IssueAge' can
be 99 for a product that doesn't allow it, or changing 'DateOfBirth'
doesn't update 'IssueAge' until the cell is edited with the individual
input dialogs.