Table is written on top of Table layout, you can just recreate the layout
and apply it again.
See the code of Table:
FYI you can debug directly into the Codename One sources to
Thanks, I'm not pushing you to make any changes more over just to make sure
I am not overlooking another package that may exist that will be more
I appreciate your support and do not want to jeopardize same.
>From what I have read, the TableLayout
JTable is pretty frustrating too... Unlike table you have more state than
the renderers/editors mess.
You can use the TableLayout directly if you prefer.
I think this is pretty doable in table with the current feature set I just
don't have the time right now to do that.
You received this
The more I work with the com.codename1.ui.table.Table and add complexities,
the more it frustrates me.
Is there a better solution in codename1 dealing with tables that are
renderable and feature rich?
On Saturday, January 26, 2019 at 8:05:11 AM UTC-5, shop.servic...@gmail.com
I can appreciate that.
com.codename1.ui.table.Table is very useful to us as we use JTables in
Our product suite is based in pure java RMI server / clients Swing GUI's
and many classes are ported to mobile devices.
We have accomplished much on the Swing side, it's very cost
That was a mistake. I didn't see it in the test case since there was no
scrolling. I guess the fix would be to keep a single listener for the
entire row and update the selected state on the component.
Then bind the listener for a specific row or create it. This
Attached is the requirement example I have in rendering a Table
Table contains one of n Estimate Groups, The 2 highlighted rows in the
attachment are a summary of the Parts / Labor that make up a Group
When we click on a column, we highlight only that column, however when we
make changes to
This method was taken from your answer to how to highlight a selected row.
Ultimate goal is to efficiently highlight a selected row
On Thursday, January 24, 2019 at 10:31:02 PM
It's because you invoke setModel() which causes the table to effectively
rebuild from scratch. You should instead update the cell/row not rebuild
the entire table.
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To unsubscribe from
Sorry, An Oversight from a cut and paste.
With only Table table.setScrollableY(true); being scrollable,
swipe down to the bottom and tap the Row 2 or 3 or 4 cells and you will see
the table scrolls to the top every time.
On Wednesday, January 23, 2019 at
You have nested scrollables here. The table and its parent container are
both scrollable and this causes confusion. Ideally it should cause an error
but these things are hard to detect efficiently in the code and you get
"weird" failures like that.
I would suggest using a non-scrollable
Mail list logo