TableView reRender gone but not forgotten

We also do need this feature back. Does not really make sense to use widget 1.0 for this.

Any news when this get fixed?

Thank you,

Ralph

+1 for next 20 days  :wink:

+1

I would like to see this include the ability to change the height of the row dynamically so we can “open” a row showing more details without having to rerender the entire table … 

Hi guys, First of all, thanks for your patience. I’ll be looking at this, i’ll update the thread as soon as i have a fix or a clear ETA. Thanks, Alex

Huh. I found a workaround, sort of, for this.

So my overall issue is I am changing a text string in a tableview row, and it is not updating onscreen. Setting reRender used to force things like this to update, but with widget 2.0, it does nothing (it seems).

In chatter on another thread, I realized I am updating an image in tableView rows on the fly in another case, and they are updating properly (without using reRender)

After reviewing the image code, I discovered that if you insert and remove elements in a tableViews row._view, the updates occur onscreen immediately (no reRender required).

Now when I render the row, I am saving a pointer to the text object that is inserted into that rows._view group, and when I want to update the string (“minutes ago” counter), I remove() and insert(newText)… And my counter updates onscreen instantly. No tableview reRender, scrollTo or anything needed. (You just have to keep a pointer to the object to be changed so you can remove it).

hi, i have the same problem too, is there any news on the matter ? it’s allmost 2 weeks old now… ?

The workaround is kind of cool in the way that you can make a smooth transition and don’t have to re-render the entire row. For example when updating a time in the visible rows with a transitions.

Does feel a bit hacky working with things named tableView._view._rows though. Also makes me scared of future compatibility.

hi, i have the same problem too, is there any news on the matter ? it’s allmost 2 weeks old now… ?

The workaround is kind of cool in the way that you can make a smooth transition and don’t have to re-render the entire row. For example when updating a time in the visible rows with a transitions.

Does feel a bit hacky working with things named tableView._view._rows though. Also makes me scared of future compatibility.

we are still waiting :slight_smile:

we are still waiting :slight_smile:

12/6/13 Alexf said "Hi guys, First of all, thanks for your patience. I’ll be looking at this, i’ll update the thread as soon as i have a fix or a clear ETA. Thanks, Alex "

we are still waiting !!! 4 months and counting

No news ? 

+1 could use it right now actually (just hit a situation where I need it)

any news on re-render?

Well, Alex mentioned in another thread that the long awaited batch of widget fixes would be forthcoming this week so fingers crossed we might have a fix for this one.

@all: as ksan says, i’m working on fixing some widget bugs. Rerendering is on that list.

alex

Any news on this ? Where exactly on the list is it ? Is it a big list ? 

Dont know about anybody else but I am loosing the will to live

We are working on getting these fixes in as quickly as we can.   These are important for us to fix.  We are not ignoring them.

I don’t have a list of what’s being fixed.

Rob

12/6/13 Alexf said "Hi guys, First of all, thanks for your patience. I’ll be looking at this, i’ll update the thread as soon as i have a fix or a clear ETA. Thanks, Alex "

we are still waiting !!! 4 months and counting