I don't mind about the character or if the folder is at the top or bottom, as long as it's not in the middle of the list.
I understand that each person has their own preferences, but I rather deal with a name most people agreed with, than having multiple folders and having to manage/delete them.
For example, if I download a macro you shared, but I don't work on it right away. Then I download 10 more macros from 10 different people and I don't work on them right away, even if I use @noisneil 's macro, I still need to go and run the macro 11 times.
Not only that, but now I need to check each one of them to find a specific macro I want to work on right now.
So I believe that dealing with a name is easier than the current scenario, imo.
Here's what I created and I would like to test if the icon is also affected or not: Test.kmmacros (917 B)
Can you download this macro, then add a custom icon to the group, create a new macro and share it so I can download it? I will add my own custom icon and see if it changes to yours when I download and install your macro. Right now, there's no custom icon on that group.
As I mentioned on my previous reply, I'm ok with it being at the bottom. As long as it's not in the middle of my personal groups, all good.
And your workaround of using the smart macro is a good option for those who want it at the top
Can you download the macro I just shared, add a custom icon, add a new macro and share it so I can see if the icon changes on my end?
And there is the problem: if I share a macro that is specific to a particular app - like Safari for example - or palette, then my macro group will have settings related to that. If you then import someone else's macro into the same macro group before dealing with mine then their macro's group settings could overwrite mine which will then result in my macro no longer functioning as intended. Consequently, you won't be able to "test" the macro of mine that your imported.
So even though your idea is well intentioned (and has merit) I don't think it will work in practice.
To be honest, I think the process of importing macros could benefit from having an extra step after double-clicking on it in Finder that tells you which group the import will go to and offers you the chance to specify a different group either new or existing.
I see what you mean.
My post is more related to our personal "test" folders, not related to specific apps, like you mentioned.
Yes, a macro related to Safari, if you share the macro from your Safari group, will go straight to a group called Safari. That's not a problem and it makes sense.
But sometimes we just share "random" macros that are not particular to any application.
That's what I would like to target, using a "universal" group.
And yes, having the option to pick where it goes, could be a good feature.
Well, even though I have a Test group and share macros from it I still sometimes have to change the group settings because I'm testing out some app-specific functionality in response to a Forum request.
But I do get what you're saying: whenever I import a macro I always try to watch carefully for the change in the Group list otherwise it can be difficult to see where it's been imported to. Although that's not so much of an issue now I have a smart group showing recently changed macros.
Ok, but now let me ask you this:
Let's say I've downloaded 10 macros from you from that "test group" and the group is set to work with any app.
Now I download another one you shared where you had to change it to a particular app.
When I install it, will it change the previous settings for that group with the 10 macros?
If so, then those macros won't work.
The thing is sometimes we download macros, but we don't look at them right away. Then we work on other macros we were working on and by the time we go to that smart group, the most recent macros are not the ones we downloaded.
Having a forum group is more straight forward imo, Avoids extra macros to run such as the one @noisneil created and avoids extra smart groups that have the issue I just mentioned
That's not what I'm using the smart group for: as soon as I do the import, if I don't see a change in the group list I check the smart group, which lets me go straight to the newly-imported macro and deal with it.
But then it's always up to the original user to share a macro that is set to use any app.
Let me clarify:
Let's say your tests folder is called "Tiffle Tests" and it's set to use any app.
I downloaded 10 macros you shared. I have the "Tiffle Tests" group now. I can test your macros and all that.
Tomorrow you share another macro, but you had to change the settings of the group to Safari. Now all the other 10 macros won't work. So in this case, I think whoever shares the macro should always revert the group to all apps before sharing. Or in that case, move the macro to a group related to the app (Safari, for example) and only then share it.
The tests group should be for macros that can be used on any app, because regardless of the tests group being yours or the forum's, you will always break macros inside if you change the group settings.
But as I said, we don't always check those macros when we download them. If I'm in a hurry and I download your macro, I won't be working on it right away. Maybe when I come back, I have other macros I would like to work on, my own macros, so by the time I check the smart group, your macro is not "recently changed"
Not sure what you mean by this. If a group is created by importing a macro and that macro is then moved to your nominated testing group (leaving the new group empty), it will be deleted.
I've updated the macro with the option to enable rather than doing it by default.
Your macro has an issue, that @tiffle pointed out:
What if the macro is app specific, such as Safari, and the group needs to be set that way?
Since your macro is triggered by any .kmmacros file, it will then move the macro to a group (the tests group) that doesn't have those settings.
So I think it shouldn't be triggered by any .kmmacros file. We should still be able to manually double click to start the process.
Maybe we could see a pop up that lets us pick if it will install in its original group or if it goes through the process of moving the macro to our custom group (if that's even possible, of course). Does it make sense?
What if that pop up you shared had 2 options, each with 2 options as well?
Status: Import Only / Import and Enable
Destination: Original / Custom Group
So with 1 pop up we could decide both things and it would still trigger on any .kmmacros file.
Fair enough and I thought about it too.
Right now, with the current macro, you can't pick, so you either do the right thing or you don't.
Looking at the images we share along with the file, sometimes we can "kinda" see if that's related to a specific app or not. For example if you are sharing a macro that is doing something global, or it only contains an AppleScript action, I know it goes to the Custom Group.
Sure, sometimes you may miss the target, but I would assume that most times you just won't. Whereas right now you will always miss it, because it's automatically doing it for you.
So I think it all comes down to having the user share that info along with the post, if the macro is supposed to be app related or not.
And that's why I think having a global tests group share by the forum users, where we know that the group should NEVER change to app specific, makes things easier. Then if we need to test with an app specific macro, we should test it inside a group with those settings.
Otherwise, if we want to always use that tests group and change the group settings, we should be mindful to revert it back to all apps.
But if it does move it to the tests group by default, what if the macro being shared is app specific? Let's say I shared a macro I created inside my Safari group?
If you download it and it moves it to the tests folder which is set to all apps, what happens?
Will the macro not work, or will the group change to Safari only?
