If you move to California, you'll find it everything is done over wine and not beer :-)
If I didn't have to deal with backward compat, I would change this behavior. It was really important when you coded everything in MXML in a text editor, but now with an IDE it seems less necessary, so, for the nost part, I agree with you. If you think you have a case that should work even given the current 'rules', file a bug so we can take a look. There might be some edge case. ________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Josh McDonald Sent: Thursday, January 31, 2008 10:53 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Re: container width > parent container's width when vertical scrollbar present I understand the "cascading scrollbars" problem, but I really have to say that's a problem with your screens if you get this. It simply means that you have to have contents that also resize. But how is that not the case anyway if it's in a container of variable width? The contents of any container of variable width must themselves be variable width or they will have either scollbars / cut off when it's too small. The problem with the way flex has it implemented is that even if everything within my container is anchored to sides or has a % width, you'll still see a horizontal scrollbar when you add too much verrtical content, and personally I call this a bug- the whole thing would have rendered correctly if the container started out as X pixels wide and I resized the browser, why should it not if the container is resized by virtue of a scrollbar instead of my mouse hand? I don't think it fair to inflict the current situation on everybody simply to release people of having to design their forms for a horizontally resizing container. There's always minWidth if you want a "screw you if you shrink my container any smaller you get scrollbars" effect. I gotta move to California so we can sort stuff like this out over a few beers :) -Josh On Feb 1, 2008 7:05 AM, dfalling <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: Thanks, I can understand that case as I've seen the scroll bars ripple down before. The only part about this that feels like a bug is how no matter how wide you make the outer container, it's always just a little bit too small to fit its contents. Any help is greatly appreciated...my current hack of disabling horizontal scrolling and adding padding is far from elegant. --- In flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> , "Alex Harui" <[EMAIL PROTECTED]> wrote: > > If you comb through the archives you'll see that this topic comes up > once a month. It isn't really a bug and is what we consider to be the > lesser of two evils. If we shrank content area when scrollbars > appeared, what would shrink a child container and cause it to show > scrollbars and all you'd see is a cascade of scrollbars. So we don't, > and you get into this situation instead. I'll try to solve your test > case this weekend. -- "Good people will do good things, and bad people will do bad things. But for good people to do bad things-that takes religion." :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
