I use the mobileGrid component in my mobile AIR app and it works great. I am really happy with it...mostly. The problem I am running into is the column widths. When I set the column widths using percentages, I get small single pixel vertical lines that show up in some of the column boundaries in the header, but not all of them. Here is an image so you can see the problem:
<http://apache-flex-users.2333346.n4.nabble.com/file/t999/image752.jpg> As you can see, the left header divider has no artifact, but the next three all have a vertical line artifact. The nice part of doing percentages is that it looks correct on every device, the column widths are all appropriately sized. The bad part of it is that your app looks like it has small unwanted and random visual artifacts, very unprofessional. I have found an alternative that displays the header with no artifacts, but it is unreliable. If you manually set the widths and round the width values in your calculations, you get a very smooth header with no visual artifacts. But for some reason, this component was made so that you have to adjust for for screenDPI when you calculate them. Because screenDPI is not always properly reported, sometimes you get columns that hang off the side of the screen. So you have to make a choice. Do I want to have proper looking headers, and run the risk of not having all of my data shown, or do I want to have visual artifacts but at least my users will be able to see everything? Neither option sounds good to me, but obviously, I have to display my data. My only option that I can think of is to skin the header to have a black bar on the right edge so even if the artifact shows up, it will blend in. What I really don't understand is why I can't just take the width of my app and multiply it time a percentage value, round it, and set it to the width of my column??? If you do the example below on the mobileGrid, it does not create a column that is one tenth of the screen width: column1.width = Math.round(appWidth * .1); That is because the documentation says that width takes into consideration DPI: "Width value is expressed in current applicationDPI, or at 160 DPI if applicationDPI is not set." I am not sure why this approach was taken, but that is where it stands today. So two questions: 1) has anyone run into this problem and can offer up a possible solution? My app is so close to being complete and this is the last little glitch I am trying to iron out. 2) Does anyone know how to get in touch with Maurice Amsellem, as I believe he did a lot of the development on this experimental component? He posted about it alot on this forum a couple years back. -- Sent from: http://apache-flex-users.2333346.n4.nabble.com/
