Trailing & Baseline Offset Unit String #35
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.
I've added properties to allow placing the unit string to the left or the right (default) of the value string. In using this library in my own project that heavily uses currencies, I found that the default position of the unit string to the right of the value was not appropriate for currencies that have leading unit characters. The unitTrailing property will place the unit string to the right (by default or if this value is YES/true) or to the left (NO/false).
Also, in looking through the open issues for this library, I noticed somebody had requested adjusting the unit string's baseline offset. The unitBaselineOffset property value will offset the unit string's baseline by the input value.
Both new properties are IBInspectable.
It should be noted that extreme unitBaselineOffset values (either positive or negative) can force the baseline offset of the value portion of the string in the opposite direction.