I just refactored the code a bit. After giving it some thought, I think that the beginEdit(), endEdit(), and isEditing() model is cleaner. Without endEdit() and isEditing(), a caller would have no way to programmatically perform these operations without casting. This means that the caller would have to know specifically which editor is in use, which isn't good.
FYI, I reverted the changes that allow TableViewRowEditor to gracefully handle the case when it is already editing and is asked to begin editing another row. I'd like to think a little more about the best way to handle this within the new API. Would you mind updating your code to work with the latest API and let me know what kind of behavior you see? That would be very helpful. Thanks, Greg On Dec 2, 2010, at 1:33 AM, lello wrote: > > Yes, that's the behaviour I mean. I tried you suggestion but it doesn't seem > to give the expected result. > > I am starting to think that the idea of the immediate flag suggested by Greg > in the other thread would be a better solution for the user. > -- > View this message in context: > http://apache-pivot-users.399431.n3.nabble.com/TableView-selectedRowChanged-tp1992938p2004375.html > Sent from the Apache Pivot - Users mailing list archive at Nabble.com.
