If you have n rows where the heights of the rows add up to more than the
height of the List, you should see scrollbars on the List.  If a row's
height is greater than the list, it shouldn't matter to the scrollbar
calc, but you can't see the whole thing due to lack of fractional
scrolling.
 
Fractional Scrolling is unlikely to ship with Moxie due to time
constraints.  We think we've left the hooks in there to make it work,
and hope somebody will get it work and post how to do it.
 
-Alex

________________________________

From: [email protected] [mailto:[EMAIL PROTECTED] On
Behalf Of Richard Rodseth
Sent: Tuesday, September 04, 2007 2:16 PM
To: [email protected]
Subject: [flexcoders] Re: Nested item renderers and scrolling



I believe my problem is due to the absence of fractional scrolling in
list controls. I ran up against the same wall in another part of the
application.

Am I correct that this is addressed in Moxie Beta 2?

On 9/4/07, Richard Rodseth <[EMAIL PROTECTED]
<mailto:rrodseth%40gmail.com> > wrote:
> I'm having a bit of scrolling trouble with a rather complex layout
> that involves nested item renderers. Imagine a list (of books, say),
> where each item is itself a list (of page thumbnails). I only want
> scrolling of the entire book list. I've implemented this with a book
> item renderer that contains a page list (which in turn has a thumbnail
> item renderer). The thumbnail list has its rowCount set to the number
> of pages (done in a binding function). I'm also attempting to
> virtualize the thumbnail list by providing a custom IList that returns
> proxies.
>
> I believe I have scrollbar policies and variable row heights set
> appropriately at all levels.
> The behavior I'm seeing is that the top level list does not get a
> scroll bar when it should. If I replace the list-based book item
> renderer with a simple label, I do get the scroll bar if there are
> enough books.
>
> I realize it may be difficult to help me without code, but if anyone
> has tried something similar, or knows of any known measuring bugs in
> this type of scenario, please let me know. Thanks.
>


 

Reply via email to