I remember running into this problem before when I was exporting macros, and then I think I just accepted having to deal with it. Now, however, I'm going to ask about it (assuming I didn't before, and my apologies if I did).
I've been thinking for a while about getting rid of currently unused macros, and today finally decided to do something toward this end by exporting and then deleting all the disabled ones. I want to have them all visible and recognizable by name, so apparently Export as Folder... is my only choice.
Why, I ask, does KM always have to create two folders when I do this, both with the same name? Maybe I could talk myself into just accepting this, but is there any reason for it? Is there any way to avoid it other than afterwards moving the exported macros to the outer folder and deleting the inner one? I guess I can just leave all of these until after I've exported from all of the groups and thus not have it hanging me up on every one, but it seems cludgy and unpleasant no matter how I do it. Thanks.
When I use "Export as Folder..." to select macros or macro groups, the file selector appears and I have to enter a name for a folder which is to include however many items there are. That seems to sensibly standardised to me (the same behaviour for 1 item or 4 or whatever). This is under V. 10.
I'm afraid I don't understand, sorry. What does the number of macros being exported matter? Whether it's 1 or 100, I would still want it or them exported to a single folder, not two with the same name. ???
So, if you select two groups, one called "Foo", one called "Bar" and choose, say, "Exported macros" as the name in the file selector, you end up with "Exported macros" containing folders "Foo" and "Bar", which each contain the appropriate macros.
This might seem like overkill if you are exporting just one or two macros, but as I maintained, "That seems to be sensibly standardised to me (the same behaviour for 1 item or 4 or whatever)." It is also more flexible for your file management.
I finally got this, thanks. What I'd written when your reply came in (for which thanks), was: "Oh, wait a minute, I think I get it. When I'm exporting from a single group, the double folder seems useless. If I'm exporting from All Macros, however, the double folder saves me the trouble of exporting from the individual groups: they'll all be automatically put into an appropriately named folder. I'm halfway through the exporting, but I'll export and delete the rest from All Macros rather than from each group, and then I can delete them all at the same time too. I might have realized this before but forgot. It's certainly handy to be able to put all the disabled macros at the bottom of the list."
Yeah, it's one of those "I know what I want to use it for" features that's really intended for something else and it had me stumped for a while -- until I tried to export from two Groups, when it became clear(er).
If you do want to export multiple macros to a single folder you'll have to work through the batch and do them individually, either driving the KM Editor UI with a macro or using AppleScript. In both cases you'll need to include the handling of duplicate names yourself (unless you like to live on the edge ).
I'm again afraid I don't understand, but it doesn't matter at the moment since I was only exporting easily doable disabled macros and got rid of around 300 of them. Some, I noticed, were ones I enable occasionally, but I'll probably realize when I run into one of these and can then dig it out or re-create it. Thanks Nige and @kevinb.
).