1. 06 6月, 2016 3 次提交
    • T
      Fixes #62. · 2092758a
      Takeshi Hagikura 提交于
      To judge the line wrapping, the padding value from the parent and the margin
      of the child being processed were missing.
      This PR adds those values when judging if a new flex line is required.
      2092758a
    • T
      Revert "Fixes the issue #62" · d665215c
      Takeshi Hagikura 提交于
      d665215c
    • T
      Fixes the issue #62 · 7b1f3a50
      Takeshi Hagikura 提交于
      This fixes the edge case where the child's width is WRAP_CONTENT and some
      of the contents along the main axis would be truncated if parent's padding
      is added (if this is the case, remeasure the child with accumulated width
      taken into account to avoid some of the contents to be truncated).
      Because accumulated width is not taken into account in the first
      measurement of each child (because FlexboxLayout has the concept of wrapping,
      at the first measurement of each child, we want the child to be big as it
      wants even if there is not enough left over space)
      
      Change-Id: I949fe6b549b5f7c10255ad5fcf6d05fb9a58eeec
      7b1f3a50
  2. 03 6月, 2016 2 次提交
  3. 01 6月, 2016 1 次提交
  4. 31 5月, 2016 3 次提交
  5. 18 5月, 2016 1 次提交
  6. 13 5月, 2016 1 次提交
  7. 10 5月, 2016 1 次提交
    • T
      Fixes #18. · 403ff8ca
      Takeshi Hagikura 提交于
      When there is a view whose visibility is View.GONE, the itemCount in a FlexLine
      isn't correctly counted in the onMeasure method.
      Thus in the onLayout method, an index mismatch was introduced.
      
      Change-Id: I7e9c3ee8b847902c9db434e38dfc0a904951f611
      403ff8ca
  8. 06 5月, 2016 2 次提交