[flexcoders] Datagrid scrollbar lag

2007-04-24 Thread Austin Kottke
Hi. I've got a datagrid with about 60 rows and 30 columns. Each
has a custom item renderer that extends a Canvas component.

The scrollbar that appears is lagging majorly with this set. I've tried 
cacheasBitmap, Implementing
different dataproviders such as XMLListCollection and other things to 
somewhat speed up the lag-also
changing framerate. It seems that the scrollbar lag stays.

Anyone have any ideas on this?

Best, Austin


Re: [flexcoders] Datagrid scrollbar lag

2007-04-24 Thread Manish Jethani
60 rows and 30 columns. So basically you have 1,800 Canvas objects.
Can you try maybe using a lighter item renderer (maybe you don't
really need Canvas?)?

On 4/25/07, Austin Kottke [EMAIL PROTECTED] wrote:
 Hi. I've got a datagrid with about 60 rows and 30 columns. Each
 has a custom item renderer that extends a Canvas component.

 The scrollbar that appears is lagging majorly with this set. I've tried
 cacheasBitmap, Implementing
 different dataproviders such as XMLListCollection and other things to
 somewhat speed up the lag-also
 changing framerate. It seems that the scrollbar lag stays.

 Anyone have any ideas on this?

 Best, Austin


 --
 Flexcoders Mailing List
 FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
 Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
 Yahoo! Groups Links






Re: [flexcoders] Datagrid scrollbar lag

2007-04-24 Thread Manish Jethani
Sorry, I thought you had 60 *visible* rows and 30 *visible* columns :)) (heh).

On 4/25/07, Manish Jethani [EMAIL PROTECTED] wrote:
 60 rows and 30 columns. So basically you have 1,800 Canvas objects.
 Can you try maybe using a lighter item renderer (maybe you don't
 really need Canvas?)?

 On 4/25/07, Austin Kottke [EMAIL PROTECTED] wrote:
  Hi. I've got a datagrid with about 60 rows and 30 columns. Each
  has a custom item renderer that extends a Canvas component.
 
  The scrollbar that appears is lagging majorly with this set. I've tried
  cacheasBitmap, Implementing
  different dataproviders such as XMLListCollection and other things to
  somewhat speed up the lag-also
  changing framerate. It seems that the scrollbar lag stays.
 
  Anyone have any ideas on this?
 
  Best, Austin
 
 
  --
  Flexcoders Mailing List
  FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
  Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
  Yahoo! Groups Links
 
 
 
 



Re: [flexcoders] Datagrid scrollbar lag

2007-04-24 Thread Erik Price
On 4/24/07, Austin Kottke [EMAIL PROTECTED] wrote:
 Hi. I've got a datagrid with about 60 rows and 30 columns. Each
 has a custom item renderer that extends a Canvas component.

 The scrollbar that appears is lagging majorly with this set. I've tried
 cacheasBitmap, Implementing
 different dataproviders such as XMLListCollection and other things to
 somewhat speed up the lag-also
 changing framerate. It seems that the scrollbar lag stays.

 Anyone have any ideas on this?

Alex Harui's blog suggests that extending Canvas in a DataGrid's
ItemRenderer is probably not a good idea if you have a lot of visible
cells, because of the overhead that comes with using a container (they
do a lot behind the scenes that you might not really need).  His
recommendation is to extend UIComponent directly and programatically
lay out your view of the item.

e


Re: [flexcoders] Datagrid scrollbar lag

2007-04-24 Thread Austin Kottke
Thanks E, I saw that post.

I tried using a DataGridItemRenderer -- extending it and putting the 
core logic
in validateNow. This is the default item renderer Its not a 
UIComponent. Is there
some speed increase by using the uicomponent?

I *still* get major lag on the scroll bar after 20 or so records.

I then remove the item renderer and its better, but its still laggy.

I'm on a dual core 2.8 p4 -- I wouldn't expect the datagrid to run this 
bad.

Any other ideas?

Best, Austin


Alex Harui's blog suggests that extending Canvas in a DataGrid's
ItemRenderer is probably not a good idea if you have a lot of visible
cells, because of the overhead that comes with using a container (they
do a lot behind the scenes that you might not really need). His
recommendation is to extend UIComponent directly and programatically
lay out your view of the item.

e