I wish it did that, too! It's the same with Swatches. I cannot drag them straight into Swatches panel.
Nope. Sadly, your way of doing it is the way to do it (or at least how I do it). That being said, I wonder if there is a script or plug-in that does this? I don't know of one personally, but I wonder how hard it would be?
yes, it would be cool if there would be a functionality in InDesign that would load all graphics of an asset to the placegun instead loading the asset itself to the placegun. As it is right now with CC Libraries not the image file itself is stored but the graphic frame holding the image.
I have to correct myself a bit: "…but the graphic frame holding the image plus the image".
FWIW: From experiments with CC Libraries using older versions of InDesign and now using them with CC 2017 I can see that sometimes its possible that links get lost. Graphics like that in principle cannot populate the placegun, but an asset using that graphic with the lost link can populate the placegun.
Let's try a feature request:
just recalled that a script by Gerald Singelmann can be of help here:
For downloading and installing read the notes by Gerald. You have to restart InDesign before three new menu items are installed with the context menu of InDesign. One of it—"Load image in Placecursor" is the one you need.
1. Drag the asset from the CC Library to the page.
The image(s) are selected.
2. Right-click with the mouse and go to "Load image in Placecursor"
3. Now that the images are in the placegun—you can remove the empty frames with backspace on the keyboard
4. and place the images in the prepared frames:
Tested with InDesign 2017 on Mac OSX 10.10.5.
Hi jersonb20949735: I just finished reading the current issue of InDesign Magazine from InDesign Secrets, and an article from Keith Gilbert clarified this issue for me. I remembered your question from the other day, so thought I'd come back and add it to the thread.
When you have graphic frames on the page, you can drag the Ps and Ai files from the library directly into the frames. It is the InDesign files that go into the library already in frames that come back out in their frames, and necessitate the cut/paste workflow you indicated above. My apologies if you already knew this, but I didn't understand the what I thought was inconsistent behavior prior to reading the article.
Can you add future images to your library directly from the source application—Ps and Ai—to avoid the extra frame issue as you move forward?
1 person found this helpful
I think I misunderstood the original post. I thought we were discussing InDesign libraries, and not CC Libraries. Either I hadn't had my caffeine yet or maybe there really IS confusion over having two very similarly-named panels in InDesign. ;-)
Thank you BarbBinder for that link. I haven't read my latest copy of ID Mag just yet. That makes total sense when using CC libraries and maybe gives me more incentive to start migrating some of my InDesign libraries to CC libraries.
1 person found this helpful
Good morning, Erica Gamet! You know what, you are the only one that got it right. The original image is of an InDesign library and Uwe's is of a CC Library and my answer addressed CC Libraries.
So jersonb20949735 —did you know you have two libraries in InDesign? (If you didn't, you do now!)
I'd suggest moving over to the new, much more powerful CC Library. It will be worth in the the long run for the reason I mentioned above, and oh, so many others.
1 person found this helpful
I did not look hard enough.
The screenshot from the OP is showing a InDesign Library.
And yes, my reply 4 was about CC Libraries and assets that were stored from InDesign:
Frames holding images, layouts that holding images.
But here is the good news:
Gerlad Singelmann's script can also be used for assets drawn and placed out of InDesign libraries. :-)
After placing the asset, it is not important anymore if a CC or an InDesign Library stored the asset before.
Just place the asset and run the new menu item from Gerald's script: "Load image in Placecursor" when the placed asset is selected. The placegun is populated with the image(s) of the selected item(s) on the page.
Caveat: A quick test is showing that you have to ungroup a placed group to have access to all the images in the group.
Maybe a bug with Gerald's script? Don't know. At least I was able to store two out of three images of a group of images in the placegun.
When ungrouping first all images will be stored in the placegun. Provided the links are intact of course.
I am still not 100% on the CC Library train for a lot of my workflow. I prefer to keep my libraries of client logos and things like my crop mark and n-up libraries locally (within client folders). That way when a client needs a logo, I know where it is within my internal workflow. Once CC Libraries has more organization available to them, I may start migrating more items over. That being said, the interoperability between apps and the CC-flavored libraries is super helpful. I'm still treading in both worlds at the moment.
unfortunately I find it harder to organize assets with CC Libraries compared with InDesign Libraries. Scriptability of InDesign libraries is not stellar, but it's ok. Scriptability of CC Libraries is a big problem. Nearly no support or if—theoretically—it could be done it is very hard to do. With no documentation available from Adobe. Literally one has to re-engineer some support scripts that give CC Libraries its functionality with InDesign. And learn from thousands of lines of code.
Alternatively I am using snippet files (idms) that can be organized with Adobe Bridge. And that MiniBridge was dropped from InDesign, yes, that hurts.
And there are some real obstacles for exchanging things between apps, namely the three big ones: InDesign, PhotoShop, Illustrator. Wheras exchanging assets between PhotoShop and Illustrator over CC Libraries is on a good way, not so with InDesign: One of the missing pieces in this jigsaw puzzle of exchange formats is SVG. If InDesign would fully support SVG (export, import, conversion to native objects), then, yes then interoperability between the three apps could be next to perfect.
Be careful of that landing!
Yeah...I'm going to stick with both for now. Neither is perfect, but I am fearful our ID libraries will silently disappear one of these versions. Help me land when I make the leap, BarbBinder ?