[SOLVED] Bug - Tableview with row.cotentWidth inconsistent

Just submitted a bug related to tableview row width (Case #29905)

Posting here the bug description to spread the info in case any other developer that faces the same problem.

This causes problem when aligning objects inside the row using row.contentWidth


BUG DESCRIPTION

The width of a row immediate before a category row is with a wider dimension than all others. This happens when:

  1. The row is the immediate before a category row and

  2. The row is being recreated after scrolling the tableview.

During initial creating, all row width are the same. Only after the re-creation (onRowRender execution when the row was offscreen and now it is on screen again) the row BEFORE a category row shows a wider width.

Real example:

TABLEVIEW CREATION (The row 4 is with the correct width in the creation):

row.index=    1      -  row width=    320    isCategory    false    

row.index=    2      -  row width=    320    isCategory    false    

row.index=    3      -  row width=    320    isCategory    false    

row.index=    4      -  row width=    320    isCategory    false    

row.index=    5      -  row width=    320    isCategory    true    

AFTER SCROLLING DOWN AND UP AGAIN (The row 4 when re-created is different width the all others)

row.index=    7      -  row width=    320    isCategory    false    

row.index=    6      -  row width=    320    isCategory    false    

row.index=    4      -  row width=    324    isCategory    false    

row.index=    15      -  row width=    320    isCategory    true    

row.index=    3      -  row width=    320    isCategory    false    

Thanks for sharing and adding this bug to our spreadsheet as well.

Ps. May I humbly suggest the typo on the thread subject to be fixed so that it appears on relevant searches? Thx

Thanks for sharing and adding this bug to our spreadsheet as well.

Ps. May I humbly suggest the typo on the thread subject to be fixed so that it appears on relevant searches? Thx

Corona said that fixed this bug on build 2014.2183.

Corona said that fixed this bug on build 2014.2183.