26
Replies
I have tagged folders on my Desktop. I seem to have no problems them when choosing File > Place in either InDesign 2024 or 2025. (Or what am I missing?)
InDesign 2024:
The colored circles represent Tags.
Here's InDesign 2025:
(Or what am I missing?)
By @Steve Werner
The problem is when searching by tag (that is, when selecting a tag in the sidebar).
By the way, I don't get it,
You \ ohter Mac usersNo one use 'Tag' folders to current projects for fast access??
By @Mendi M
I understand that it can be useful. However, as @Steve Werner has already mentioned, everyone has their own workflow. Plus different ways of visual and mental perception.
I use tags mostly for faster visual recognition of certain folders in the Finder (in combination with utilities that restore the normal appearance of tag highlighting in the Finder as opposed to the tiny, shameful, barely visible circles introduced by Apple several years ago).
For quick access, I just add the desired folders to the sidebar.
For an effective search by tags, I would need to:
-first, remember to tag the folder;
-second, remember the connection between the specific colors and specific folder names (and if I decide to change a tag color, I'll have to redraw this mental connection map yet again).
To me it's just much easier to find a folder by its name in the sidebar.
Once again, I understand how searching by tags can be efficient for many people with certain visual perception preferences. My answer, hopefully, explains why it's different for others.
hm, I wonder if it's because InDesign's Place dialog cannot place folders, but only files?
By @Laubender
Yes! You nailed it.
I can now confirm that that's exactly the case. And it's not actually an InDesign issue. That's how the macOS navigation dialog behaves.
That is, if an app issues a command to display the navigation dialog where the user is only allowed to choose files (but not folders), then the tagged folders will not appear when searching by tag.
It's unlikely Adobe can do anything about it. So I think we can safely remove this uservoice request. An appropriate feedback can be sent to Apple to change this behavior (which, frankly, I don't think will change anytime soon).
Btw, after discovering the AppleScript behavior described above, I realized that you can use this AppleScript to place files, in which case you can search folders by tag as desired:
set f to choose file
tell application id "com.adobe.InDesign"
activate
tell document 1 to tell place gun 1 to load place gun f
end tell
It works great!
Unfortunately, we must have the options like 'Show import option',
If there was - I would definitely set it as the default place command.
@leo.r wrote:hm, I wonder if it's because InDesign's Place dialog cannot place folders, but only files?
By @Laubender
Yes! You nailed it.
I can now confirm that that's exactly the case. And it's not actually an InDesign issue. That's how the macOS navigation dialog behaves.
That is, if an app issues a command to display the navigation dialog where the user is only allowed to choose files (but not folders), then the tagged folders will not appear when searching by tag.
It's unlikely Adobe can do anything about it. So I think we can safely remove this uservoice request. An appropriate feedback can be sent to Apple to change this behavior (which, frankly, I don't think will change anytime soon).
Sorry, that's not true,
1. cmd+o works perfectly in tagged folders.
2. in Illustrator the place also works in tagged folders...
Why is it so important to you to remove that uservoice request? it's useful for many users who tag project folders
Sorry, that's not true,
1. cmd+o works perfectly in tagged folders.
2. in Illustrator the place also works in tagged folders...
By @Mendi M
Well. When I use Cmd-O in InDesign, it behaves just like the Place command, that is no tagged folders are displayed when searching by tags.
However, this does indeed work differently in Photoshop and Illustrator, that is tagged folders are found when searching by tags. Same applies to some other apps, but not all.
I don't have an explanation for this. This behavior doesn't seem to be consistent between apps. Maybe there are some subtle API differences when dealing with the navigation dialog between various apps (just like the ones between AppleScript and native Cocoa, as discussed earlier).
AdChoices
