This finally fixes #91 EntryAlignment bug on iPad. It turns out that on new cell creation, the width value appears to be hardcoded at 320. The correct value is only recalculated on cell reuse. This causes the initial value for cell.ContentView.Bounds to return the wrong value. I wish there was a more elegant solution, but this does the trick for now.
This finally fixes #91 EntryAlignment bug on iPad. It turns out that on new cell creation, the width value appears to be hardcoded at 320. The correct value is only recalculated on cell reuse. This causes the initial value for cell.ContentView.Bounds to return the wrong value. I wish there was a more elegant solution, but this does the trick for now.