Laganama

EDIT: Title updated "1.9.3 …" since all issues, except 9., continue in v193. / + Added "10. DPI column content cropped"d
EDIT 23jun21: + added "11. Shortcut Key conflict"
====
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 ] The DPI column content gets clipped once it got moved outside + removed. (see post below) When navigating in the RM and trying modifier keys + arrow keys then some of them trigger & alter text properties (leading, kerning, baseline shift). This must not happen with a separate UI window in foreground, in particular not if an item of the RM is selected in the layout/layers panel. 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
10. The DPI column content gets clipped once it got moved outside + removed. (see video below)

 

Does one know what "missing content" means? (appears at a .PDF and a .SVG)

Also I want to add a suggestion to the topic's panel improvement list: The column "Status" appears to be redundant if the column "Placement" would be used instead. As far I understand  an Embedded resource never can be Missing + every Modified resource must be a Linked resource.
So it could work to have in "Placement" 4 variables/entries:
_ Embedded (= 'OK')
_ Linked (= 'OK')
   _ Modified (linked)
   _ Missing (linked)

EDIT: "– Modified" added to the variables

Wish: support for Text Variables. Very handy e.g. to define revision numbers and other stuff and inject document metadata (date printed, modified, created, etc.) at appropriate places. Makes the document more evolvable (maintainable).
Wish++: share Tet Variables across documents (Designer, Publisher, Photo).

As a workaround you could...
1. Group the multiplying image + the objects which shall be overprinted
2. Set the Group's blend mode from "Passthrough" to "Normal".
 

Not talking to anyone in particular here. Just recording more of my thoughts for Serif to take into consideration...
All major regex engines are case sensitive by default. Therefore I believe APub ought to have, as suggested in this thread, its engine changed to be case sensitive and change the switch to Match Case to be Case Insensitive AND to provide a Reset button on the Regex main screen so one doesn't need to vist a flyout just to see if that flag is set.
Optionally, just use up some screen real estate and move the flyout options to the main screen and get rid of the flyout--but still make the default to be case sensitive. 

According to the Boost documentation, [[:lower:]]/[[:upper:]] are case classes that are "class names [that] are always supported by Boost.Regex."
The case sensitive flags are used for "literal strings" to allow, or disallow, case sensitivity.
Pretty much as simple as that, Walt. Now we could go on arguing what those statements mean and how they apply to APub...but that's mostly meaningless without one of the developers stepping into this discussion and explaining the rationale of their implementation of this/these features.
We seem to simply disagree on how case classes are implemented and APub's requirement to also add the case flag sticky setting to do what a case class is intended to do without it.
It's not a big deal in the larger scheme of things--unless one is coming from other applications that interpret/implement the Boost library differently. In the case of APub, there are X number of people coming from InDesign (and others) where such a flag (Match Case) isn't even present as the person doing/constructing the regex is expected to follow Perl/Boost regular expression syntax.
So when such a person is expecting Perl/Boost compliance comes to APub, threads such as this will be written wherein you (or others) can feel free to write the explanations of how to do it in APub. This will/may be more an issue if/when scripting ever comes to Affinity applications.
OK. Now I'm really done flogging this dead horse.

This still seems slow to me (in Affinity Publisher 1.8.2). Compared to how this forum scrolls for example (and anything else actually), the pages / spreads studio scrolls way too slow. Looks like it scrolls only one line at a time, disregarding the global scroll settings.

scroll speed is too slow on pages

When I scroll over pages in the pages menu, the speed seems extremely slow. Anyone else experience this? IMO, it should be quicker.

You do not always want a color to global overprint, sometimes, you just want one element to overprint, nevertheless what color it is in.

Thank you guys, this issue is fixed in 1.8.3. Everything works as usual.

@Laganama Just to clarify, there actually was a shift-selection issue in 1.8.2 that is supposed to have been solved in 1.8.3 (just released). For example, one of the bug fixes in the 1.8.3 beta cycle was this one:
Please report back if the issue you are describing is not resolved by 1.8.3

Hi both,
This works as expected on my end in 1.8.3 
With no objects selected, Shift + Drag selects the objects With a mix of both selected and deselected objects, Shift + drag selects new objects and deselects the pre-selected ones With only selected objects, Shift + Drag deselects objects.   

Hi there,
here you can download files suitable for Slovak and Czech hyphenation. Copy them to the directory according to https://affinity.help/publisher/en-US.lproj/pages/Text/hyphenation.html.
hyph_cs_CZ.dic
hyph_sk_SK.dic

Thanks @walt.farrell, now it is correct.

Great, 1.7.2 fixed this issue. Thanks.

It would be very useful to have functions to select the same:
 
Color fill stroke (color / width) Appearance To quickly select all your outlines, or background element in 1 color. 
Speed is everything.  :)

When "Add Layer" is clicked, make it appear in the hierarchy next to a selected item. Also if multiple items are selected and if "Add Layer" is pressed, automatically put them inside the new layer.

from the designer help folder

-

-

Also put GREP in paragraph style

I’m so totally stoked about this beta. I have spent a couple hours poking around, and I can say that this beta is further along than I expected. I have high hopes that this will in time replace Indesign for us (a small publisher), and it looks well on track.
Among several features that wowed right away and other "missing features" that I can work around, the one thing that stood out for me is the lack of GREP searches. In Indesign, I have a small series of GREP searches that I have saved over the past years, and I run nearly everything through them. A couple minutes on a typical file, and I have made several hundred changes. When I work on a book, the changes are in the thousands. (Note: I publish in French, and French typography relies heavily on non-breaking spaces; these GREP searches help me rapidly put them where they ought to go.)
While you're there: being able to save the searches as presets would be ideal. And as not everyone is familiar with GREP, a few pre-saved searches would help provide them immediate use: remove multiple spaces, remove trailing space, etc.