Wed 16 May 2007 06:09:12 PM UTC, comment #2:
Using code "May 16 04:32:35 2007 UTC", I no longer observe the
original issue. I think it would be best to ignore focus, particularly in the case where multiple cells are selected because it can be difficult to see.
If multiple cells are selected, I would expect all selected cells to run, regardless of focus. However, if only one can run, logically I would expect the first 'selected cell' to run, not the cell that has focus.
On the other hand, if a cell has focus but is not selected, I would expect the first cell to run. Using the original defect parameters, let's say the user selects the second then third cells. The focus is on the third cell. The user decides against both and, holding down the CTRL key, uses the mouse to click on cell two, then cell three to unselect them. I observe the third cell has focus, but is not selected. CTRL/R. Since the third cell has focus, I might expect the third cell to run. However, ignoring focus, it makes sense that the first cell runs since
nothing is selected.
|
Fri 11 May 2007 02:47:21 PM UTC, original submission:
Using lmi-20070425T2112Z and xml_notebook_coli_boli.xrc,
when requesting to run a specific cell in a census, the
system does not always run the cell requested but instead
runs the first one.
Consider:
File | New | Census
Add cell, two times (total of 3 cells)
Highlight cell 1 - change age to '35' <ok>
Highlight cell 2 - change face to '2000000' <ok>
Highlight cell 3 - change age to '55'
change face to '3000000' <ok>
Cell 3 is highlighted.
Ctrl/R.
In the open window, I observe that cell 1 ran and not
cell 3 as I requested.
Close window. Again, cell 3 is highlighted.
Highlight cell 2 then go back and highlight cell 3.
Ctrl/R.
I observe the illustration for cell 3.
In order to run a cell after editing, the user must
move off the that cell and come back to it. This
behavior is observed with other skins.
|