thomaso

No, unfortunately it's not fixed. Left: first the frame was created, then the image placed via place tool –> causes a shift on replace (see magenta frame fill). Right: first the image was placed (dto.) then converted to picture frame –> causes a massive shift off the page on replace (same occurrence in v191 beta & retail) v998 replace shifts.m4v Still not working for convert, for tool partially only: • A frame's custom saved default stroke gets applied but a custom saved fill does not – regardless of the way of new frame creation (tool or convert) or of a previously used frame fill. • The custom saved default properties No Scale + No Anchor aren't respected if the frame is created via convert. Instead still the factory defaults get applied (fit max + center). • For both ways of frame creation a custom default fill may get achieved with an additional use of the button "Revert Defaults" (whereas with factory defaults the fill gets applied during frame creation). And: still missing a certain selected layout resource when opening the Resource Manager – instead of a selected folder, which makes it more cumbersome to detect the selected single item). Plus various UI issues in this window.

I would expect if "Apply to Selection" is active a picked colour would get applied to a current selection only. Whereas … … on an image layer with this option off a picked colour indeed does not get applied when picked – but as soon the picked color (its well) gets clicked then again it gets applied to the entire layer, not to a selection only. … on a pixel layer the active option "Apply to Selection" doesn't cause a picked colour getting applied at all, neither to the selection nor to the entire layer. That feels confusing, doesn't it? – Is there a misunderstanding with the term "Selection" in this option?

With your .afpub I don't get the issue when exporting with the '(for print)' preset: Affinity_Forum.pdf Can you upload this page from the PDF you had sent to the printer? And possibly a screenshot of your export 'More' settings? Did the printer request any specific PDF format or profile?

Using a blend mode for color masking doesn't work sufficiently if back- & foreground contain a similar total range (of color, brightness, saturation – depending on the mode). The issue occurred in your first image, too, but was less obvious because the sky was closer to bird's bright parts (in both brightness and hue). Your second image has a darker + more colorful sky which makes the "darken" / "darker color" mode less efficient than wanted because of being more different in the bird's bright parts. However, it will be easy to mask the birds, e.g. via the selection brush tool and copy/paste the selected bird only, not the entire image as in the workflow before.

deebz, these jumping buttons were reported a few times by others for versions before v191. – How about your grid view in separated vs non-separated & new vs old .afpubs?

1. Separated Mode: New documents in v1.9.1 don't display a useful grid. The grid appears partially only, its offset varies with the page position within the window, its scaling doesn't fit to its setting (1 cm ≈ 2 cm). A document created in a former APub version doesn't show this issue. An app relaunch doesn't prevent from this bug. v191 grid bug.m4v 2. Non-Separated Mode: When switching to non-separated mode then the bug jumps from New documents (v191) to the earlier (initially created months before 191) – while the grid in the new .afpubs appears as expected. Note: see here also the missing paper white in the older .afpub. This issue occurs since many versions every time I toggle between separated / non-separated mode. v191 grid bug 2.m4v

[v.1.9.1] When I option-click in the Layers panel a layer's thumbnail to display only this object in the layout & main window then each page icon in the Pages panel gets altered and shows this selected object only, all master page icons included, even though this object in fact exists on only 1 layout page and no master. The visual delay seems to indicate that the issue demands more additional CPU / GPU than changing 1 single page (spread) icon would need. layer opt-click icon display alone.m4v

The links in my post refer to a bunch of threads, containing several answers, some from a couple of hours ago, others a few days ago. And there are even more related topics, with varying keywords like e.g. replace, picture frame, resource, image, size, scale, property. The forum's search indeed can be cumbersome because of it's lack of "fuzzy" search. Alternatively you can use an internet search with adding the "site:" attribute ("site:forum.affinity.serif.com"), optionally limiting it to the APub/mac-bugs forum, for instance… … with all these 7 terms: 8 results: https://www.google.com/search?client=firefox-b-d&q=replace%2C picture frame%2C resource%2C image%2C size%2C scale%2C property site%3Aforum.affinity.serif.com%2Findex.php%3F%2Fforum%2F81-publisher-bugs-found-on-macos%2F … with only 3 of this 7 keywords: ~200 results: https://www.google.com/search?client=firefox-b-d&q=replace%2C picture frame%2C resource site%3Aforum.affinity.serif.com%2Findex.php%3F%2Fforum%2F81-publisher-bugs-found-on-macos%2F

Answers were given a few times. Feel free to use the forum's or internet search… https://forum.affinity.serif.com/index.php?/tags/afb-4537/ https://forum.affinity.serif.com/index.php?/topic/136717-temporary-delay-in-serif-staff-responding-on-these-forums/

No. But I experienced Affinity try such reinventions, sometimes for no or hardly lucid reason. There's no taboo for ID comparisons but they can fit or can be a helpful idea – or maybe useless & confusing. For instance in case of unknown concepts or especially if "ID's inline object behavior is also somewhat weird".

Sure? Your or any user's idea doesn't have to be congruent to Serif's. That's why it's useless if you try to answer my question, instead of a Serif team member. (if "inline" has wrapping 'by nature': what's the nature of "inside"?) For me, your comparisons with InDesign make the discussion unnecessarily complicated and confusing. ID is not the mother of APub, Serif works completely independently of Adobe. Saying "I'm used to it like this from Adobe..." sounds strange, considering that APub obviously is not interested in copying the UI/UX of InDesign. From this point of view, ID doesn't matter at all. What counts is the concept of Affinity (which might meet ID's but doesn't have to). That's what I was/am asking for.

That's why I specifically asked Gabe , I am interested in the developers view. According to your arguments also "Inline" pinned objects wouldn't got by default their built-in text-wrap feature (one may want to use blend modes...).

@Gabe, I wonder whether "by design" at all… 1. an object pinned "Inline" is expected to wrap text across more than 1 column within a text frame? 2. an object pinned as "Float" and set to "Inside" is expected to cause text wrapping (…like pinning "Inline" does automatically according to its "border" settings)? Or whether a Float object would require by default an additional text wrap setting if "Float" is set to any of the 3 "Inside" options? In case of the latter: • Why doesn't it stick to its pin-position? • What is an use case of pin float inside but without text wrap?

In my experience with this preference file copied from a beta folder it worked to give access to saved presets even when the "Create" option was grayed out. Since it appears to be fixed here in macOS 10.14 Mojave it is possibly influenced/caused by the macOS version? @Mgn, what macOS are you running?

Still in 1.9.1 the Resource Manager UI appears buggy in various ways: When a resource is used more than 1x then RM shows it within a folder. If a resource gets selected on page then the RM doesn't select the according entry but the entire folder instead. Makes it quite cumbersome to detect/select a specif layout item in the RM. Sorting by name doesn't work consistently. Expanding the window width widens the "DPI" instead of the "Name" column, maintaining cropped file names but useless empty space instead. The text layout in the details section insists in wasted space to its left but crops long text entries instead, e.g. profile names or dimensions. Navigation in the entries via keyboard (up/down) doesn't update the details section and requires to mouse-click the entry instead. Searching for a missing resource doesn't display the missed file name in the following window's title bar and requires instead window moves to make long or complex file names visible behind. Re-linking a missing resource via RM > Replace doesn't allow to auto-re-link other missing resources in the same folder but requires to re-open the .afpub + "Yes" instead. [ Re-linking missing resources when opening an .afpub + choosing "Yes" doesn't re-link all missing files even if in the same folder. ] [ Replacing a resource of a picture frame doesn't maintain the frame properties <– is already reported in various threads ] 1. When a resource is used more than 1x then RM shows it within a folder. If a resource gets selected on page then the RM doesn't select the according entry but the entire folder instead. Makes it quite cumbersome to detect/select a specif layout item in the RM: 2. Sorting by name doesn't work consistently: 3. Expanding the window width widens the "DPI" instead of the "Name" column, maintaining cropped file names but useless empty space instead: 4. The text layout in the details section insists in wasted space to its left but crops long text entries instead, e.g. profile names or dimensions: 5. Navigation in the entries via keyboard (up/down) doesn't update the details section and requires to mouse-click the entry instead: 6. Searching for a missing resource doesn't display the missed file name in the following window's title bar and requires instead window moves to make long or complex file names visible behind: 7. Re-linking a missing resource via RM > Replace doesn't allow to auto-re-link other missing resources in the same folder but requires to re-open the .afpub + "Yes" instead. 8. Re-linking missing resources when opening an .afpub + choosing "Yes" doesn't re-link all missing files even if in the same folder. –> see https://forum.affinity.serif.com/index.php?/topic/136142-resource-manger-missing-images-bug/&do=findComment&comment=750650 9. Replacing a resource of a picture frame via RM > Replace doesn't maintain the frame properties <– is reported for v1.9.1 already in various threads