it's virtually possible if you dropped more N images first and drop exactly N files after, but is kind of an unexpected behavior because users are not aware of what the icon<->file association will be.
I think is safe to say this feature requires custom UI to work, so if more people have your necessity we are open to taking this feature into consideration.
Hey patrick, I'm not sure I understand what you mean by is kind of an unexpected behavior because users are not aware of what the icon file association will be
My example is a bit different from Patrick's, but it seems somewhat methodical.
(Not sure my attachments will match up with these 5 steps, but hope they will)
I start with PNG files A-Z and 0-9 (34 PNGs total) -- and drag them all to the app's drop palette.
You can see that when I click the numeric "34" arrow, the app has accepted all 34 PNGs... (Though yes, a UI showing 34 tiny file representations would be way more clear to a user than seeing this obscure number, especially since I don't natively count the number of PNGs I batch-drag to a target)
But in this workflow, I next choose my desired Export icon file types -- in this case case I have chosen .ICNS files ... I also didn't have to choose an output shape format since my PNGs were all circle-shaped with transparent bg's... Now I will click "Export".
Though I could have named the batched output folder "icons A-Z and 0-9", I left it default showing file output type icns and the number of converted files (34) ...
And indeed 34 different .ICNS files are generated.
So clearly there is a basic logic already in the app to do batch conversions, and if I also wanted to have a matching set of 34 iconized FOLDERS, I would just repeat the process by clearing the drop palette, then dragging the source PNGs to the app palette, this time selecting "Folder" as my export file type, and I would get my batched output folders...
But I do follow that Patrick's desired batch action is somewhat different. Nonetheless I do agree with him that batch-processing is a very normal expectation from consumers. Though I do use the app for one off operations, I almost always have a batch I want converted all at once. And so I recommend this indeed be placed into the app task queue. Thanks! -- Richard
Hi Patrick, my mistake, sorry, I thought i was addressing the person from
company who answered first. I actually understood perfectly the first time
what you're trying to do, and it's a great use case. ... That's why I
referenced several times that YOUR use case was different from mine-- I
totally got that re: direct automated iconization of your source files.
I wrote (to the company rep) questioning *his phrase about file types. *And
I wanted to affirm that yes there are other users who want a variety of
batch processes so yes, put resource time into this.
first of all, I have to say you (@quicksite) made the best possible explanation of how the batch processing work. Congrats :)
I think the point is we miss a way to apply icons in batch and right now I'm not sure which is the best way to handle this specific task. In software terms, this means to allow users to handle N icons to M files/folders association where N and M are number and may differ. We can make new UI to handle this but may result in a really complicated interface.