On Thu, Oct 8, 2009 at 09:24, skar <[email protected]> wrote:
> Yup, tableModel.setValue does the job. I was using setRows previously which
> also worked fine. However, what I want is the state to be like before the
> save was attempted.
>
> Before pressing enter, the user has the celleditor open with his new value
> and the tableModel has the old value. Now, I have restored the old value to
> the tableModel. But the celleditor has the old value, not the new value he
> tried. That way, any long change he made with a small mistake can be
> corrected easily by the user.
>
Hmmm... The cell editor factory is passed col, row, xPos, value, and table.
Since it gets the table, you could have previously used table.setUserData()
with the new value, and pull it into the cell editor in the factory.
Just a thought.
Derrell
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
