Pixelkobold

Hey Mr. Ash thank you for your clarifying words above, thought I don't see any need for them. You did an awesome, marvelous job on v2 and as a customer whos been around for years now, I think the 40% off starting price for v2 is more than each customer around can wish for. I gladly would have paid even the full price, since I think that even this is (200 for the whole stuff) is more than fair. So what I want to say is, unfortunately you can't make it right for anyone, there are always some out there who has sth to complain. Keep on that awesome work Gordon

didn't thought about that, but that does make sense somehow

Same problem here. I find the new feature awesome, but I don't see why it is necessary to download and install all the addons from serif shop into all three different apps seperatly and so triple, especially since some of them are really huge and need diskspace on the systemdrive which I dont have to spare. I agree with sfriedberg. The possibility to give at least a specific folder for the addons (on antoher harddrive) would be great. I see that it could be difficult for brushes, but I think for assets and such it wouldnt be a great problem to have that function anyway serif, you do a great job, I live your apps. Keep on like this

there is in Publisher Go to "Manage Resources" in the document Menu and on that tab you click on "collect" (down by the buttons) BUT BEWARE!!, this will change all the links in your original document to the new location of the collectd photos, so I appreciate to make a copy of the document before "collecting" and save that instead of the origianl document file

For me its the same and its a very nerving issue. I mean, why do I have the option to set a style from an object with effects, when it doesn'T apply the same on another object. f.e. I set a dropshadow with a certain value, which I want to use all through the document. So I save it as a style to use it on the next object, but nada... if I apply this to another object, the shoadow looks wholly different and I have to set the pixel values for it again. I believe that must be a bug (since I know that InDesign didn't do it that way), so please, Serif, correct that soon. Otherwise, your apps are really awesome, I love publisher so much Thanks for all ;-)

err... I don't know exactly what you want to know. I usually put up picture frames, arrange them and then fill them with photos. If I need text I put a textframe there and fill it anyway, after finishing my first yearbook in APub, I see in both ways (embedding and linking) some advantages. I think its just a personal thing which way you use photos and so on

okay thats a possibility. I will see to it. Thanks a lot for your help

yeah you're probably right. thought I don't understand why every new pcitures I drag into a frame is turned wrong way around, even if the original photo is oriented correct. Nevertheless I guess I didn't think through this far enough :-)

yeah that would do the trick, but it is not how I like to do it, since I don't always want to use the "replace" dialog which pops up, but instead just drag & drop from the other app (xnview) from the second monitor, which is much faster and easier

Hi there I've used the search function but didn't find anything about this, so I start a new topic I find this "issue" very annoying in Publisher, especially because it costs a lot of time. Perhaps I doing sth wrong or I miss a function/preference for this, so I just ask /explain I usually fill my Picture frames via drag&drop out of XnView or the Explorer (under Windows10), because I find this way the most comfortable. So I have a page setup f.e. with a lot of picture frames and I set all of them to "maximum scaled" and "middle". Usually I fill the first frame with a picture and rotate it in place, too. But when I copy this frame and drag a new photo in the copied frame, all is set to zero and the image is neither rotated right nor set to the right fitting. I find this very annoying, since it costs time and a lot of unnecessary clicks to adjust every single frame. Any suggestions? Thanks

yes that would be a good work around. I use JPEGMini, which is awesome for such jobs. I give it a try Anyway, as soon all the pages are completely loaded (which takes a few minutes when you have linked photos), the publisher runs smooth. I used to use InDesign with photobook projects similar to this in count of pictures, and never good such issues when loading a document. (though I realize Publisher is in its first version while ID is in v14 or sth like this.) so probably this could be a posting for the bug or request area?

there you have a point I not thought about. I'll try that, and make a copy before doing so thanks

Hey there what is the better alternative handling a lot of photos in Publisher at the moment? I do a photo yearbook for my daughter with probably a few hundred photos (I dont know exactly yet how much it will be). I am not through with it yet (doing November at the moment) and I see that when you open the document, Publisher needs a lot of time to open all the pages (e.g. load the linked photos) In the meantime the PC reacts sluggish for minutes. When all is loaded there is no performance problem anymore, but during loading the document there is no working possible I wonder though, if it would be better if I embedd the photos instead of linking them... any suggestions to that? Thanks

@Paul I guess you just have to go into publisher in your assets and click on the three small ines, there is an option for "import assets". click there and then go where the file is Its a guess, havent tried it yet ah and btw: you sure you arent in the beta version for customer accidently? (only if you have installe dthe beta along the release version) I had the issue with the asset earlier too, but then I recognized that windows opened up the document I clicked on in the BETA and not in the release version two different softwares and then you dont have the asset in the beta you have in the normal release version

EDIT: forget it, I see that this should be fixed with the new beta. So I have to wait until the 1.7.2 Release update