Open GoogleCodeExporter opened 9 years ago
If you resize the elements in runtime you need to revalidate or animate we
don't retest size changes due to the major performance overhead of seamlessly
reflowing the UI.
Original comment by shai.almog
on 6 Sep 2012 at 4:43
But isn't the purpose of setShouldCalcPreferredSize(true) exactly to signal
that the size of an element has changed and its size should be recalculated?
The documentation for setShouldCalcPreferredSize says "Indicates the values
within the component have changed and preferred size should be recalculated",
and that's also what I understood from your answer on the forum thread
mentioned above.
Original comment by ch.hj...@gmail.com
on 6 Sep 2012 at 5:39
It signals that but it doesn't trigger the actual layout. E.g. 20 components
changed in different layouts. setShouldCalcPreferredSize would be invoked for
all of them but validate() can be invoked only once.
Original comment by shai.almog
on 6 Sep 2012 at 7:15
OK, I think I've spend far too much time trying to figure this out myself.
Basically, what I'm trying to achieve is the List fisheye effect, but with
variable size list elements as ContainerList allows. Something I believe iOS
and Android supports. I'll ask the question in the forum.
Original comment by ch.hj...@gmail.com
on 7 Sep 2012 at 5:10
We explicitly supported fisheye for list but never tested it in ContainerList,
I think it needs explicit support. I'll convert this to an RFE and assign it to
Chen who might have some input here since he worked allot with the fisheye in
the list class.
Original comment by shai.almog
on 7 Sep 2012 at 5:20
Original issue reported on code.google.com by
ch.hj...@gmail.com
on 5 Sep 2012 at 8:24