I have a proposal for changing the way we handle the reconcile cell. Right now, here's how this cell works: The 'enter' callback tells you what to set the new value of the cell to. Thus, when you click on the cell with the mouse, you 'enter' it and the value changes. You can't 'edit' the cell as you would, say, the description. When you're outside the cell, there's no way to get to it from the keyboard, which makes sense given the above semantics. However, once you're in the cell as the result of a mouse click, if you start traversing the register up or down with the keyboard, you 'enter' each successive reconcile cell and change each one as you go. This is rather strange, unintuitive behavior, I think. Also since (as far as I know) there's no way to tell in advance whether a cell will behave this way, every time you click on a cell that is already active, you have to reenter just in case the value needs to be changed like this. This makes for some contortions in handling the regular cells in a sane way, and also makes for some inefficiency. I would like to flag cells which behave like the reconcile cell (currently I believe it's the only one that does) so the GUI knows which ones it needs to reenter even when they are already active. This will also allow the register traversal code to better avoid these cells for non-mouse traversals. comments? dave -- Gnucash Developer's List To unsubscribe send empty email to: [EMAIL PROTECTED]
