Closed GoogleCodeExporter closed 8 years ago
Original comment by romannu...@google.com
on 31 Jan 2012 at 12:36
Output file names can simply be the same as input file name with a prefix.
Original comment by ahmettim...@gmail.com
on 10 May 2012 at 2:20
I don't understand the problem. You can already change "example" to whatever
you'd like, using the name field in the generator.
Original comment by romannu...@google.com
on 10 May 2012 at 4:18
I am talking about Launcher icon generator. There is no name field. It is
always ic_launcer.png.
I dont use this tool for only launcer icon.
Other tools dont help me. For example, in a listview, I use an image in every
row. And I want that image in different sizes: xhdpi, hdpi, mdpi ldpi. (More
options would be better).
Original comment by ahmettim...@gmail.com
on 10 May 2012 at 6:55
My original idea seems to be already implemented on the page for "Menu Icons".
Great work, thanks!
Original comment by ser...@gmail.com
on 10 May 2012 at 7:02
@romannu I think you understood what I meant. Can this tool be a generic image
generator tool rather than only a launcher icon generator tool? If we could
define drawable sizes for different densities, that would be better. I mean I
want to be able to have 160*160 sized image instead of 96*96(default) for
xhdpi.
Original comment by ahmettim...@gmail.com
on 11 May 2012 at 10:58
Same would be good for the device frame generator, currently when I drag the
generated image back to the desktop, it always has the name 'png.png', but it
would be good if the original filename could actually be kept, so that
splash.png remains splash.png. If it's possible in Chrome to read out the
original filename, such feauture would be very helpful; right now I always need
to manually rename the file back.
Original comment by mathias....@gmail.com
on 2 Jun 2012 at 5:29
The launcher icon generator is not intended to be a generic icon generator. For
that, see http://code.google.com/p/android-ui-utils/issues/detail?id=50.
As for the device frame generator, that's an interesting point, let me look
into that.
Original comment by romannu...@google.com
on 13 Jul 2012 at 4:35
Original issue reported on code.google.com by
ser...@gmail.com
on 27 Jan 2012 at 4:52