I can sense your frustration, and the tone of your answers are trying my patience. There are a lot of variables here, and it is not my full time job to support you through this. I know you've spent lots of time on it and it can be a real pain in the butt to figure out some things in Flex, but please don't take it out on those of us who are trying to help. I'm trying to help as many people on this forum as I can so I generally don't have the capacity to remember all the details of your issues, and that will occasionally cause me to steer you in the wrong direction, since I can't see all of the hazards on the road ahead of you. Since my recommendation of not sizing the image to 100% didn't work, it is probably that there is some factor I didn't consider, but I am recommending best practices here, so what you take away will hopefully serve you on your next Flex task. I think I recall that you had swfs with sizes like 300x175. How big do you want them to show up in your component. At their true size or scaled down in some way? I think I also recall asking you to post a couple of the swfs so I can see what they look like. Please do so in your next response so I can try to get a better understanding of why sizing these swfs is not working as expected. There is always going to be a chance that you'll have to do something one-off, but I haven't seen enough evidence that we really have to do so. Also, if you have a sketch, screenshot or any other visual that can give me an idea of what your goal is that will help too. -Alex
________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of droponrcll Sent: Wednesday, October 03, 2007 2:18 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: MultiPurpose ItemRenderer --- In flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> , "Alex Harui" <[EMAIL PROTECTED]> wrote: > > That is correct, medaiObject is the API for component time, and data is > mapped to it when it is a renderer. > > You have to dispatch an event for binding {} to work. Use of [Bindable] > without an event causes us to wrap the property in a getter/setter pair > which would be redundant in your case. > > In the code I proposed, the image is not 100%. When you do that, the image is far bigger than the container, causing all sorts of nasty side effects, including scrollbars. > I'm not a fan of making > things really big when only a portion of it is 'filled'. I'm just a fan of things that work, regardless of whether they're 'correct' or not. Taking the 100% off of it means that the image doesn't shrink into the container properly. >I think you > should set scaleContent="false" as well. How will that make things better? Even with scaleContent set to true, the content doesn't actually shrink the way it should. I suspect that there are some esoteric undocumented rules somewhere about when and how content actually scales, but so far the only thing trial and error has shown is that the image _has_ to be 100% or some percentage of the container in order for it to work. Thanks for staying with me on this. I am getting very frustrated.
