You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 8, 2021. It is now read-only.
Hey Dave, this is a great tool! I'd love an enhancement for exporting as squares, as currently it provides a button that's sized in a way that the image has to be re-sized after export to be used in an element like a UIButton or UIImageView.
For example square.and.arrow.up.on.square exports as a 59x85 asset, which when placed in a square button looks awful.
My proposed solution would be to provide an option to export as squares, so the 59x85 asset would become 85x85, with the 59x85 content portion centered in the asset.
Thanks a lot!
The text was updated successfully, but these errors were encountered:
Would you want this for all export formats, or just pngs? Like, should the UIBezierPath code generate a bezier path that's square, but has a centered path within that square?
I think with bezier paths it wouldn’t be a bad option, though not as essential as images because of the difference in where people tend to use paths vs. images.
If squares and export size are turned on together then you could probably pair the two by first squaring, then changing the size.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hey Dave, this is a great tool! I'd love an enhancement for exporting as squares, as currently it provides a button that's sized in a way that the image has to be re-sized after export to be used in an element like a
UIButton
orUIImageView
.For example
square.and.arrow.up.on.square
exports as a 59x85 asset, which when placed in a square button looks awful.My proposed solution would be to provide an option to export as squares, so the 59x85 asset would become 85x85, with the 59x85 content portion centered in the asset.
Thanks a lot!
The text was updated successfully, but these errors were encountered: