Table not passing through changes immediately in write through mode.

Vaadin 6 / 7 / 8 Framework UI
1

Hi

I am using Table in write through edit mode and noticed that it does not write the edits done in cells immediately to the item property values. The updating to items seems to be delayed until table is scrolled down so that row disappears from view or if user navigates away from page etc. Is this behaviour by design and is there some way to force the writes to happen as soon as cell loses focus?

Regards,
Tommi

2

Another issues with the table on 6.4.1 I noticed:

If you have several pages of rows in your table then swithing to edit mode and back changes the row height which in turn seems to mix up the scroll bar. When you switch back from the edit view and then scroll to bottom you do not see any rows as the non edit mode rows take less space vertically.

-Tommi

3

Hi!

Works as coded. The default field factory (that table uses to create fields for properties) creates non-immediate text fields by default. Changes from non immediate fields are saved to a buffer on the client side until another component needs a server visit.

The other issue is theme dependent. Do you have your own theme or is it with a standard vaadin theme? Fields in Table should be styled to consume the same height as a normal text. It has been like this with Vaadin at some point, but I don’t know if it is like this anymore.

cheers,
matti

4

Hi

Thank you for the replies.

Would it be useful development idea to change the fields to respect the table immediate attribute? In my case the container is collecting the changes so they are not immediately updated to data store. Immediate events to the container would allow the container to have up to date data dirtyness information from the table.

The theme in use is runo default theme. Is this a bug in the theme and should I report it?

Regards,
Tommi

5

Hi!

It sounds like an issue in the theme, but I couldn’t reproduce the issue with our old test application:
http://demo.vaadin.com/FeatureBrowser

Can you build a reduced test case and provide details on the environment where the issue can be reproduced?

cheers,
matti

6

My mistake here. I was testing with the Eclipse builtin browser.

Regards,
Tommi