-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Different size icons not being handled correctly #6
Comments
Hi @pfiaux, thanks for report. I'd like to ask you to provide all the files involved as well (SVG sources, generated SVG sprite and PNG sprite). Please send them to joschi [at] kuphal [dot] net — thanks! Also, please note that the online version at iconizr.com is based on the original PHP version and quite outdated at the moment (the Node version has far more features and options to consider). Unfortunately, due to limited resources, I won't be able to work on your request in the next couple of days, so please don't expect me to be too fast! Sorry for that. Cheers, |
I thought the site might be running the PHP version, since i noticed that was indeed more options in node. This is why i'm confused that it behaves differently on the same icon set. Files on the way. |
@jkphl did you find time to have a look at the issue already? |
@Red-nothing Sorry, no, not yet! :( I'm so totally overloaded at the moment that there is no time for working on side projects right now. Thanks for your patience! |
Hi @pfiaux & @Red-nothing, just wanted to let you know that I didn't forget your issue! I'm going to start a rewrite of iconizr during the next days and will ensure that your assets render correctly in the new version! Cheers & happy new year, |
I tried generating a sprite sheet with a set of icons that have different sizes. This worked correctly on the online version of iconizr (they all get scaled down to the specified size).
In the node version the generated spritesheet was messed up in different ways:
Is there a way to handle different sizes or is this a limitation?
The text was updated successfully, but these errors were encountered: