-
4 Mar 2013 4:14 PM #31
i know this is old but
i know this is old but
for anybody else trying to fix this, i had the same problem and fixed it with this. In my grid view i setup listeners and used the deffer function like the user suggested above inside of the painted method to refresh the list. It's hardly noticable and you can adjust the time it deffer's for for a quicker or slower responce.
Code:listeners: { painted: function(){ Ext.defer(function(){ this.refresh(); }, 50, this); } }
-
14 Mar 2013 5:46 AM #32
Hi all,
I am experiencing quite similar issue when using itemTpl config for each list item.
Did any of you experienced the issue with an 'Ext.dataview.component.ListItem'?
I am considering using ListItem instead, since it takes so much time to solve (I have posted a similar issue on Dec 27), and there is still no available fix in the new 2.2 beta 1 also.
Roei.
-
29 Mar 2013 4:58 AM #33
To all Sencha developers
How is the fix coming along? Any planning you guys could share with your users? A lot of users would like to see this fixed - the issue is reported months ago and obviously quite some different users are affected.You found a bug! We've classified it as TOUCH-3781 . We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.
Please check this thread as well. It might be the same issue - why is that thread marked 'Closed' actually?
-
29 Mar 2013 5:08 AM #34
@Razris right, this is a major issue for me also.
It certainly holds me back from moving forward with my project.
-
1 Apr 2013 8:34 AM #35
-
15 Apr 2013 2:02 AM #36Sencha Premium Member
- Join Date
- Mar 2013
- Location
- Insch, Aberdeenshire, Scotland
- Posts
- 7
- Vote Rating
- 0
This worked for me on a Ext.dataview.List, it's a bit counter intuitive but the list is rendering properly:
It seems to take itemHeight as a min-height and then adjust for anything bigger. I know itemHeight supposedly defaults to 47 but explicitly setting it worked better for me.Code:variableHeights: true, itemHeight: 47,
You found a bug! We've classified it as
TOUCH-3781
.
We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.


Reply With Quote