Matthew Twomey

I have started a new Publisher document and placed all 51 pages of a 17mb pdf file. I used the method where I draw a picture frame on the first Publisher page, then place the PDF and select all the pages and finally click in the picture frame. I set my default image placement to "linked" (rather than "embed"). The placement works just fine and all 51 pages come up just as I'd like them. I can see in the resource manager that the PDF is marked "linked". However, when I save this file, it saves as a 900+mb file and I can't seem to figure out why?

Aha! Ok, thanks. Well, zeroing out my bleed is a better workaround than have to have Photo open separately.

This makes it impossible to correctly do advanced selections on more complex shapes. It works fine in Photo V2. I'm running the latest version as of today on OSX Ventura. This same procedure works fine in Photo V2.

So is there no way to add this back to the context toolbar?

@Old BruceHa ha ha! Excellent :-) Also a huge fan. I need to catch up on it!!!

@Old Bruce - I think you simply misunderstand how this works technically, and why the registration approach mentioned in this thread adds zero additional risk above / beyond the risk of you simply sharing your keys or installing it for someone else using your own ID. Perhaps you overestimate the simplicity of basic piracy without any special hoops or tricks. But at this point, I think this is me -> So I'll leave it be - I think it's clear to most at this point.

Patric, yes - and also: It would be registered to your account. Same as if you'd just given her your keys (or did the install as yourself, on her computer).

Exactly.

You are incorrect, and your responses may mislead people. This has nothing to do with "giving anyone your apple ID and password". It also has nothing to do with Affinity having some kind of privileged access to the app store (which they don't). As an app publisher myself, I can tell you it's a common practice to KYC "know your customer" by having them register post purchase from the app store. I have the MAS version and upon registering it (within the app), Affinity does indeed know I have purchased the app (because you can't register the app unless you've purchased it). In fact I have several entitlements, from Affinity, that require that I have purchased and registered the app. Why some folks think this is technically infeasible is beyond me - companies do it all-the-time. It is true - that if you "do nothing" and don't take the step to register the app, there is no way they can know you've bought it. But that's besides the point of this thread.

It does just seem like an advert for their paid product....

Once purchased from the MAS you can register your app to Affinity. They certainly can identity you and your purchased app, if you allow them to (through registering it).

Thanks - that helps. I lose the group name, but still easier than what I was doing..

Is there a shortcut way to do this? Right now, when I want to do this, I have to click the first object in the group, scroll down to the end and shift-select the last. Not a huge deal, but can be time consuming when I have a group of like 100 objects. I run into this when I want to do something like distribute the objects or rotate them individually but at the same time.

Ahh, ok thanks. So I see they aren't there in Acrobat. However, they are still there when I print from Acrobat. Is the best way to get to a PDF that can print sans these artifacts, to rasterize those areas before exporting, or is there a better workaround?

I feel like I might be missing something simple, but I can't see, to get rid of these white gaps (on PDF export) without rasterizing the whole thing first (which I don't want to do). 60 second video with a very simple demonstration. Any tips here?