Fixes #91 EntryAlignment bug on iPad #156
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit 4db55d0.
…eation, 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.
migueldeicaza
added a commit
that referenced
this pull request
Nov 5, 2012
Fixes #91 EntryAlignment bug on iPad
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.