A better way to operate QR Code in Swift, support iOS, macOS, watchOS and tvOS.
MIT License
Bot releases are hidden (Show)
Published by ApolloZhu over 1 year ago
EFCirclePointStyle
to respect isTimingPointStyled
settings.Published by EyreFree almost 3 years ago
EFPointStyle
protocol to allow customizing foreground point style.EFPointShape
is deprecated. Use EFPointStyle
instead.Published by ApolloZhu over 3 years ago
This release contains breaking changes, in addition to those mentioned in v6.0.0!
Wonder what's new in this official V6 release? How do I fix those new warnings? Check out the migration guide here: https://github.com/EFPrefix/EFQRCode/discussions/115, or watch the video demonstration on YouTube 或者 bilibili.
EFQRCodeGenerator
configuration methods.EFQRCodeGenerator
properties are now public.EFQRCodeGenerator.clearCache
can be used to free up memories used for caching results.EFWatermarkMode.rectForWatermark(ofSize:inCanvasOfSize:)
can be used to calculate the frame for watermark image in a canvas.EFQRCodeGenerator
configuration methods to be more consistent.
EFQRCode
and reordered convenience generate function arguments to be consistent with generator methods.EFQRCodeGenerator
now caches more generated contents to improve performance.EFQRCodeRecognizer
expects non-nil image and returns non-nil array of results. The returned array may still be empty.EFIntSize
is now an immutable, final class.CGColor
extensions white
and black
to omit first argument label.EFQRCodeGenerator
and EFQRCodeRecognizer
is now fully available to configure/use in Objective-C.EFQRCodeMode.none
is now deprecated. Use nil
and EFQRCodeMode?
instead.EFUIntPixel
is no longer a part of the public interface.pathToSave
parameter.EFQRCode
is no longer available in Objective-C. Use EFQRCodeGenerator
and EFQRCodeRecognizer
instead.Core
and watchOS
subspecs #100.
Yes, I should have named release 6.0.0
as 6.0.0-rc.1
, but I guess it's too late now :P
Published by ApolloZhu almost 4 years ago
This is a PRE-RELEASE. We will introduce breaking changes (with migration helpers) in the next (few, pre-)release(s) without bumping the major version (i.e. for v6). We will, however, try our best to use proper release sequence (alpha, beta, release candidate, etc.) for future major version releases (e.g. v7).
Core
and watchOS
subspecs #100.
Published by ApolloZhu almost 4 years ago