Allows fix for issue #19 where Images set are always Template. #20
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.
Basically a fix for #19 (Request: Allow non-template Images or Access to the ImageView in some way) which allows for an Boolean value,
setImagesAsTemplate
, to be set on theSVPulsingAnnotationView
which determines whether images added to theimageView
andheadingImageView
are to be the exact image that you give it, or rendered as Template images. Without this fix, any images given to these Image Views are set with theUIImageRenderingModeAlwaysTemplate
Rendering Mode.This fix is much better than the subclass "hack" seen in issue #19, with only 4 line changes compared to having to subclass, override two methods, and access the private
imageView
property through searching the subviews.The changes don't break anything in the master branch and the new Boolean defaults to YES as to not change anything for those who would update to this commit and still want the Rendering Mode defaulting to Template.