Comments on: Setting the requested row count on an FxList control in Flex Gumbo http://blog.flexexamples.com/2009/02/25/setting-the-requested-row-count-on-an-fxlist-control-in-flex-gumbo/ Just a bunch of Adobe Flex Examples Mon, 13 Feb 2012 01:38:13 +0000 hourly 1 By: Simon http://blog.flexexamples.com/2009/02/25/setting-the-requested-row-count-on-an-fxlist-control-in-flex-gumbo/comment-page-1/#comment-8234 Simon Wed, 18 Aug 2010 20:40:59 +0000 http://blog.flexexamples.com/2009/02/25/setting-the-requested-row-count-on-an-fxlist-control-in-flex-gumbo/#comment-8234 Ok thanks Peter, I actually just tried simply using an example from the docs with a DataGroup and renderer and the same things happening. I ensured the second item was not visible and no dimensions set whatsoever, still happening, I will file it as a bug ta. Ok thanks Peter, I actually just tried simply using an example from the docs with a DataGroup and renderer and the same things happening. I ensured the second item was not visible and no dimensions set whatsoever, still happening, I will file it as a bug ta.

]]> By: Peter deHaan http://blog.flexexamples.com/2009/02/25/setting-the-requested-row-count-on-an-fxlist-control-in-flex-gumbo/comment-page-1/#comment-8233 Peter deHaan Wed, 18 Aug 2010 19:52:50 +0000 http://blog.flexexamples.com/2009/02/25/setting-the-requested-row-count-on-an-fxlist-control-in-flex-gumbo/#comment-8233 @Simon, I believe that is correct, but there may be a few other things happening. For example, if the Spark List skin has a <code>minWidth</code> or <code>minHeight</code> property set and a second item renderer may possibly be slightly visible causing a second renderer instance to be created. It'd depend on how big your list is vs your item renderer dimensions. If you think there is a bug, file a bug report at http://bugs.adobe.com/flex/ and include a simple, reproducible test case and somebody on the Flex SDK can investigate. Thanks, Peter @Simon,

I believe that is correct, but there may be a few other things happening. For example, if the Spark List skin has a minWidth or minHeight property set and a second item renderer may possibly be slightly visible causing a second renderer instance to be created. It’d depend on how big your list is vs your item renderer dimensions.

If you think there is a bug, file a bug report at http://bugs.adobe.com/flex/ and include a simple, reproducible test case and somebody on the Flex SDK can investigate.

Thanks,
Peter

]]> By: Simon http://blog.flexexamples.com/2009/02/25/setting-the-requested-row-count-on-an-fxlist-control-in-flex-gumbo/comment-page-1/#comment-8232 Simon Wed, 18 Aug 2010 19:36:13 +0000 http://blog.flexexamples.com/2009/02/25/setting-the-requested-row-count-on-an-fxlist-control-in-flex-gumbo/#comment-8232 Hi, Am I right in saying that if you set the requestedRowCount=1 and ensure that the layout has useVirtualLayout=true then only the first rendered item will instantiate a new Renderer instance? I am noticing that even though no height or width properties are set (as the docs specify, these render requestedRowCount useless) _2_ renderer instances are actually instantiated in my tests? Any tips on where things could be going wrong? Cheers, Si Hi,

Am I right in saying that if you set the requestedRowCount=1 and ensure that the layout has useVirtualLayout=true then only the first rendered item will instantiate a new Renderer instance? I am noticing that even though no height or width properties are set (as the docs specify, these render requestedRowCount useless) _2_ renderer instances are actually instantiated in my tests? Any tips on where things could be going wrong?

Cheers,

Si

]]>