Oops, should have added that, here you go: 29399
Thanks!!
Thats a nasty bug that makes your app look like unprofessional cr*p. i was under the firm impression that it was going to be fixed asap
Let’s hope Alex is back at work this week and has nothing else on his plate for a while…
Kerem, I am not sure its under Alex’s umbrella. Regardless, its a complete show stopper. I checked the release notes of the recent builds and it really doesnt look like it has been fixed.
Not to beat a dead horse, but it’s really bad in IOS 6. The unwanted X axis shift is 50 pixels or more 
Not a dead horse at all - its as bad with the Android theme as well.
Not fixed as of 2122. It’s not too bad if you decide to make a game called … Chase the wiggling button. Aimed at 3 year olds. How about it.
Hehe 
thats right down the alley of the “guess what you clicked on the segmented control” game
All bugs and jokes aside, anyone tried the SplitView yet? I’m looking for some feedback and improvement. If nothing else this will help newcomers see how to update widgets programmatically etc.
Alex, we have a 3 course meal and then some waiting for you. Please push all other distractions aside! Let’s start the year with a Big Bang. Thanks for all your efforts. All the best!!!
Has there been any resolution to the scrollview and segment control?
So far no resolution from CL. We’re keeping fingers crossed for another batch of widget fixes soon. The wiggling switch issues (mentioned above) have been resolved though.
Well in the meantime I may have a fix, using a master detail listview featuring images that link to the content. Not the best, but it may do the job. ksan you have more experience in this than me, why can’t many of the features of corona support scaling? Its seems that many of the major items such as scrollview/listview/ tableview can’t. Is there a way around implementing scaling for these?
I just played with this for a bit and I threw out the scaling restrictions. It turns out table view scales just fine, but you have to use row.height and row.width not row.contentHeight and row.contentWidth as they get scaled and position things wrong when used in onRowRender. The only issue I’ve seen is that the top category row is slightly off on the y axis when scale is less than 1, but that can be fixed. I think the restriction is a leftover from G1 where you had fixed mask images that couldn’t be scaled.
You can actually put a tableView in a group and scale the group without changing anything in the widget source but then I noticed the top category row is shaking (yes shaking). That would have to be looked at as well.
Good luck
Has there been any resolution to the scrollview and segment control?
So far no resolution from CL. We’re keeping fingers crossed for another batch of widget fixes soon. The wiggling switch issues (mentioned above) have been resolved though.
Well in the meantime I may have a fix, using a master detail listview featuring images that link to the content. Not the best, but it may do the job. ksan you have more experience in this than me, why can’t many of the features of corona support scaling? Its seems that many of the major items such as scrollview/listview/ tableview can’t. Is there a way around implementing scaling for these?
I just played with this for a bit and I threw out the scaling restrictions. It turns out table view scales just fine, but you have to use row.height and row.width not row.contentHeight and row.contentWidth as they get scaled and position things wrong when used in onRowRender. The only issue I’ve seen is that the top category row is slightly off on the y axis when scale is less than 1, but that can be fixed. I think the restriction is a leftover from G1 where you had fixed mask images that couldn’t be scaled.
You can actually put a tableView in a group and scale the group without changing anything in the widget source but then I noticed the top category row is shaking (yes shaking). That would have to be looked at as well.
Good luck