On 2/10/06, tobiaspatton <[EMAIL PROTECTED]> wrote:

> Well, your suggestion *almost* works. Click on "Beta" a couple
> times, and you'll see the "Alpha" row's size being increased, though
> no button is added.

It did work for me.  :-?

> I could fix this by adding:
>
>     <mx:SetProperty property="height" value="60"/>
>
> to the "openState" state declaration. I have no idea why this would
> work :(

Strange.  I was expecting that the cell will resize to accomodate the
new button.

> On that note: how can I better arm myself to sort out these problems
> on my own? I've read the documentation on custom renderers and
> states, but nothing in there would have led me to your conclusion
> that the list was "shuffling" cell renderers. Is there more I can
> read? Books? Sample code? Blogs?

Oh - that's because I'm one of the developers who worked on that code.
 You *could* figure out what's happening by using a debugger and
stepping into the framework source (not sure it works), but I wouldn't
bother.  It would be nice if the framework source were available for
everyone to see :)  I'd also love to document some of the component
internals (especially the *why* of things), but it's one of those
things....

Here's the feed for my Flex blog:
http://feeds.feedburner.com/mannu/flex

Here's the Flex smart category from MXMA (RSS):
http://weblogs.macromedia.com/mxna/xml/rss.cfm?query=bySmartCategory&languages=1&smartCategoryId=5&smartCategoryKey=D0399B4B-9A76-7F68-06E1F26F3451C3AE

Here's some other developer blogs:
http://weblogs.macromedia.com/mchotin/
http://deitte.com/
http://coenraets.com/index.jsp


--
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

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/flexcoders/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 


Reply via email to