twolfson/grunt-spritesmith

Wrong retina image detection

Closed this issue · 1 comments

Gruntfile.js

        sprite: {
            target: {
                src: options.sourcePath + 'img/sprite/*.png',
                dest: options.sourcePath + 'img/sprite.png',
                imgPath: '../img/sprite.png',
                destCss: options.sourcePath + 'scss/inq/_sprite.scss',
                retinaSrcFilter: options.sourcePath + 'img/sprite/*@2x.png',
                retinaDest: options.sourcePath + 'img/sprite@2x.png',
                retinaImgPath: '../img/sprite@2x.png',
                algorithm: 'binary-tree',
                padding: 2
            }
        }

log:

Running "sprite:target" (sprite) task
>> Normal sprite has inconsistent size with retina sprite. "./img/sprite/section-1.png" is 60x60 while "./img/sprite/section-10-small@2x.png" is 80x80.
>> Normal sprite has inconsistent size with retina sprite. "./img/sprite/section-10-small.png" is 40x40 while "./img/sprite/section-10@2x.png" is 120x120.
>> Normal sprite has inconsistent size with retina sprite. "./img/sprite/section-10.png" is 60x60 while "./img/sprite/section-11-small@2x.png" is 80x80.
>> Normal sprite has inconsistent size with retina sprite. "./img/sprite/section-11-small.png" is 40x40 while "./img/sprite/section-11@2x.png" is 120x120.
>> Normal sprite has inconsistent size with retina sprite. "./img/sprite/section-11.png" is 60x60 while "./img/sprite/section-12-small@2x.png" is 80x80.
>> Normal sprite has inconsistent size with retina sprite. "./img/sprite/section-12-small.png" is 40x40 while "./img/sprite/section-12@2x.png" is 120x120.
>> Normal sprite has inconsistent size with retina sprite. "./img/sprite/section-12.png" is 60x60 while "./img/sprite/section-13-small@2x.png" is 80x80.
>> Normal sprite has inconsistent size with retina sprite. "./img/sprite/section-13-small.png" is 40x40 while "./img/sprite/section-13@2x.png" is 120x120.
Files "./scss/inq/_sprite.scss", "./img/sprite.png", "./img/sprite@2x.png" created.

For anyone curious, this issue is a duplicate of #132. Please see that issue for solutions/workarounds