machadodesign

Experiencing the same problem here also. iMac 27" running Mac OS 10.14.6 and Publisher 1.8.3. Like tnwalkinghorse, I was working in a document that has a tables on several pages. The text frame is on a separate page from the tables but still experiences the space instead of delete.

As much as I try to exclusively use Affinity apps for my studio I constantly run up against shortcomings that seem so glaring. Not supporting spot color export in EPS files is one of those shortcomings that seems so basic that it kind of boggles the mind. If this was a version 1.0 product I could understand, but if Serif really wants these apps to be regarded as professional apps then these kind of omissions need to be addressed. I own and love every one of the Affinity apps, I just wish that I could rely on them more.

Trying to export a file as PDF/X-4 and I get an error every time. The error occurs with any of the PDF/X formats. All assets are linked CMYK files. I am on Publisher version 1.7.3 but the problem existed on 1.7.2 also. System I am working on is an iMac 5K with 24GB of RAM running on MacOS 10.14.6. I have isolated the problem to a block of text the has bulleted text. The font is the same font that is used elsewhere in the document so I doubt it is a font issue. I deleted objects in the document one by one and tried to export until it was successful and then when the text block was replaced the error is repeatable.

The lack of this feature is rapidly becoming a make or break feature for me. I spent a ridiculous amount of time this morning trying to get a bullet list to wrap correctly around a photo and it is pretty much an impossibility in Publisher as it exists now. For some bizarre reason the space between the bullets and text wants to bounce around when the text is wrapping an irregular object. Why would the distance that is set not remain the same and the left edge just move over. Frankly I find more and more features in Affinity apps that leave me scratching my head trying to figure out the rationale they are using. Maybe it's a product of being on different sides of the pond, but I seriously doubt it. This seems like it would be such a quick fix. Can you guys please move this up the punch list?

I linked an existing text frame with overflow text to another existing unlinked frame that had no text and the default text size was set to the same as the overflow frame (12pt). When I linked the second frame the overflow text came in at 2.4pt. If I changed the size of the overflow frame text to 12pt, the text in the original frame changed to 64pt. Also when selecting all (command-a) I would expect all text in the chain, meaning both frames, to be selected. Publisher only selects the text in the frame where the cursor was. This is really wonky behavior and I would have expected this to be resolved before releasing an app.

Hello, is there any function in Publisher that emulates InDesign's "Indent to here" character? I have found the function to be useful in formatting lists but can't find anything similar in Publisher.

When editing a layer that has a mask using the Mesh Warp tool, it only effects the image layer and not the mask which then makes the mask not align with the image and is completely worthless. Am I doing something wrong? This seems completely illogical.

Thanks R-C-R the Live Filter works perfectly and I too am not sure why it would be different than the perspective tool. I love Affinity Photo and Designer but there are still a lot of things that I find extremely counterintuitive.

If I use the perspective distort tool on a layer that has a mask I cannot see that there is any way to make the tool affect the layer and mask together. This is a real hassle to any workflow that has images with masked layers.

This is more of an annoyance than anything else. When you have an object drawn on a page in AD 1.5 and you haven't yet applied a fill or stroke, if you scroll the page the bounding box and handles disappear until you stop scrolling. It makes it difficult to scroll to the edge of something without starting and stopping to see where the edge is. A solution is to add a fill or stroke but it is an extra step I shouldn't really have to do.

Please see my question on this thread https://forum.affinity.serif.com/index.php?/topic/11042-selections-do-not-transfer-over-to-new-layers/

Can you please explain the logic in having and image layer versus a pixel layer? Isn't an image made up of pixels? I can understand having embedded object layers so that the object won't be modifiable, but image vs pixel just seems confusing and silly.

I drew a selection on a photo and wanted to create a new layer with copy of what was selected. In 1.4.3 it was a simple command-J and it was done. In 1.5 beta 6 it doesn't work. It makes a copy of the entire layer. I even tried doing a command-C copy and then paste and it still copied the entire layer, completely disregarding the selection I made with the marquee tool. Went back to 1.4.3 and it works fine. Restarted the 1.5 beta 6 and it still doesn't work. Definitely a bug.

Yep, that resolves it. I'm not sure why Serif seems to have such odd ways of doing things. I understand there is a learning curve with any new app, but there are a lot of things that just seem counterintuitive. Thanks for helping me get this figured out.

I'm not sure why Serif is so set on using DPI in an image app. It makes little sense since DPI is a measurement used in the output device such as a plate making system for offset printing. Imaging apps use PPI or pixels per inch and Serif is unnecessarily complicating things. Worse still is the fact that the resize without resampling doesn't work correctly and the file will still import into InDesign as 72ppi. There needs to be some serious thought put into this before the next rev.