Le 03/04/2016 22:26, Igor Stasenko a écrit :
On 3 April 2016 at 23:00, Thierry Goubier <[email protected] <mailto:[email protected]>> wrote: Le 03/04/2016 21:51, Henrik Nergaard a écrit : A FTTableContainerMorph recreates all its submorphs on every drawOn:. Not correct. Ok. I stand corrected. This is why it is done in #drawOn: and not #drawSubmorphsOn: Submorphs are only recreated when the view of the list has changed #canRefreshValues, ie if the variable "needsRefreshExposedRows" is set to true. If this is false nothing will happen in #drawOn: If changes is necessary the drawOn: will recreate submorphs for the current view (showIndex) and set the "needsRefreshedExposedRows" to false signalling that it is correctly laid out. What is interesting, still, is that submorphs rebuilding (deleting and recreating them) happens during a #drawOn: call, and that it is fast enough not to register on the time needed for a world redraw. And so I still think it is interesting for Igor to have a look at FT :) Only for review purpose, i guess. From what you described, as i wrote in previous post this is not new to me. I think i seen some kind of morph(s) that was using same technique in the past. it may be different in details, of course, but overall idea was same: create and use as many UI elements, as many fits on the screen, not as many items in the list(s)
Yes, probably. Regards, Thierry
