MikeA

(...)

(...)

The contents of the master page text frame are still editable but the selected frame is actually on the master page rather than the ‘normal’ page, which is where I think the confusion (whoever’s confusion it is) may be. It’s probably more of a ‘philosophical’ question: “When is a selected layer not selected? When it’s on a master page but you’re not editing the master page itself.” Or something like that.
The Edit Detached command should open a red ‘banner’ at the top of the canvas window which has a “Finish” button which lets you go back to the page, see attached image. "Detached" in this case can be thought of as a temporary detachment as only some of the properties of the master page layer are being detached during editing.

Interesting.
I have been able to quickly confirm that this is indeed the case on Windows 10.
I wonder if it is the same on OS X.
I also wonder if it’s happening because the text frame on the master page isn’t actually on the ‘normal’ page and, since it’s not on the ‘normal’ page the software thinks there’s nothing to deselect. In other words, there’s nothing selected on the page so nothing can be deselected.
P.S. Using “Edit Detached” on the master page allows deselection by the normal methods.

I am in no way an expert on Affinity's text styles, but after using APu > Preferences > Miscellaneous > Reset Default Text Styles to return the text styles to factory defaults, I opened the Base style for editing in a new document & got this:

Note that down in the Style settings text box "Leading Override" appears twice, first as "0 pt" & then as "auto," but in the Character > Position & Transform section it is set to "Auto."
I have no idea why it appears twice in the settings text box -- maybe it is because the Base style is a group style, but that is just a guess. However, "Auto" does seem to be the actual default "Leading Override" Character panel setting for any style based on the Base style.

I'm not sure which thread you mean, but the common reason for confusion seems to be that some users don't understand the difference between "leading" and "leading override", and try to use the leading override setting in the Character panel when they should be using the leading setting in the paragraph panel. You're the first I've seen sho has raised this other issue, which I will need to study further before I can comment meaningfully.
 

@BryceB
Thanks for making that video. One thing I noticed in the discussion about regular expressions: unless Affinity Publisher's implementation of regexes is different from what I used in Perl, then:
.*
means not "one or more of any character" but "zero or more of any character." If you want "one or more," use:
.+
If Affinity Publisher supports this, there's also:
.?
... to mean "zero or one of the preceding character or expression (in this case: "any character"). Now of course I'm going to have to find out if it also supports greedy vs. non-greedy matches. How time will fly...
It was interesting to see that you were able to use "$1" for the "captured" buffer. A comment I saw here a couple of days ago used "\1" instead. So then I thought: Affinity Publisher must require "\1" rather than "$1". Clearly it doesn't.
In Perl, "\1" can be used in the replacement string but is more likely to be used within the search string — to refer to something captured to a buffer via parentheses — within the same search string.
I was surprised you were able to use "Apply 'Body' to Paragraphs". I would have thought the command should be "Apply 'Body' to paragraphs and preserve character formatting" (or "...and preserve local formatting").
After reading that Publisher doesn't yet support style merging, I'm tempted to go about it this way:
1. Style everything precisely as needed in the word-processing program (I use the Softmaker Office editor called TextMaker, which writes .docx format).
2. Import the word-processor file — Publisher will create new styles named to match those of the incoming document.
3. Tell Publisher just to delete all unused styles in the document.
Wonder if it'd work. :- )
 

Thanks Wosven! I tried your workaround and it worked for me. To remind myself how it works (and for those who aren't find & replace experts) I posted a screen capture to YouTube showing how I follow your steps. The search and replace with regular expressions is a little tricky if you've never done that kind of thing before.
Preserving bold and italic text when importing to Affinity Publisher.

Issue:
In my Affinity Publisher documents, I tend to use the same text styles. When copying and pasting text between the documents, the styles get duplicated with a number added at the end. This happens even if the styles are identical. Example:

^ These are all the same style which have been duplicated when copy & pasting between documents. 
Solution:
When copying and pasting between a document, Affinity should ask the user how handle duplicate styles rather than just numbering them.
 
Here is an example of how it could work:

This dialogue box would pop up whenever copying and pasting text in situations where Affinity would currently just duplicate the style.
This dialogue box would be optional, activated first via an option in preferences, so users who like the current handling of style can chose not to activate the option. 
Merge Styles - Keep incoming definition This option will cause the two styles to be merged. All values will follow the source document. 
Merge Styles - Keep local definition This option will cause the two styles to be merged. All values will follow the local document. 
Create new style - This will create a new style (which is how Affinity currently handles it by duplicating the style and adding a number to the name).
Additional options:
Clear Overrides - Any differences between the local and incoming style will be discarded. 
Keep Overrides - Any differences between the local and incoming style will be kept as overrides. 
Save Overrides as character style - The differences can be saved as a character style. 
Example:
I have  "Document A" which has  text that has a style called "English translation". This is just Helvetica, bold text 12pt. 
I copy and paste this text into "Document B" that already has a style  called "English translation". If I select "Merge Styles/incoming" then the style from Document A will be used. If I click clear overrides, then any differences between the text in document A&B will be lost. 
 
Who would this be useful for:
This would be useful for users who regularly copy and paste text between Publisher documents. 
 

>> Zero is not "no override". No override would be the value you see in the Character panel before you make any changes. For Arial, the Character panel will show a default of (if I remember correctly) "(12.4 pt)".
Yes, I finally saw that 'zero' doesn't mean 'no override'. For now I'm assuming that selecting ’auto' for the Leading Override value is the right thing to do if you want to ensure that you're getting precisely the baseline-to-baseline height you specified in Paragraph > Leading.
Once you select Character > Leading Override > Auto and confirm it by pressing Enter or Tab, the value shown in the Leading Override field immediately changes to the same value that you previously set in Paragraph > Leading.
It wouldn't hurt for Serif to expand the documentation in that part of its online help file, explaining the behavior a bit better. They could, for example, include an example. :- )

It is probably confusing mostly because it is implemented not as a paragraph attribute but as a 'local' character attribute, even though it affects everything on the same line of text as the character(s) the override is applied to.
IOW, leading override is really a text line attribute, but since in Affinity there is no separate text line attribute panel it is included in the character one.

I was under the impression that Leading was applied to whole lines of text rather than a set of consecutive characters within a line.
While Publisher allows you to apply a Leading Override to a set of characters I think it determines the actual Leading for the whole line of text by taking the largest setting that has been given to any of the characters in that line. Therefore, if you set some characters Leading Override to be 5pt while the rest of the line has Leading Override of 12pt, the line will use 12pt. On the other hand, if you set the characters Leading Override to be 24pt while the rest of the line has Leading Override of 12pt, the line will use 24pt. Does that make some kind of sense? (That’s how it looks to me but I don’t use Leading Override a whole lot, except to make all of the lines of text in a paragraph further apart or nearer together.)
If you want to shift a few characters up or down then you can use the Baseline Override setting just above the Leading Override.

I agree also. It would be a benefit for all.
Particularly  Display of specific style information

-

-

-

Hi @MikeA  : You tag like this:
type the @ sign and the first few characters of the name you want. You'll see a list of possible names. Click on the one you want. In your case I had to type in your entire name MikeA as there were so many names that began just with Mike. Just typing an @ in front of some existing text doesn't seem to work. You have to begin to key the letters following the @

Check out the private messaging options also if you just have a private message for someone. In Windows I right click on the person's tag and open in a new browser tab. It shows me their personal info and there is a button to click for sending them a private message.

Look at the actions at the bottom of the Text Styles panel:
It would still be good to know if this is (a) your mistake, (b) a Mac vs Windows thing, or (c) a 1.7 vs 1.8 thing

As a new user, @MikeA might find it interesting to read the longish thread that began 1-1/2 years ago concerning the preferences dialog and its useless Search. If it's any consolation, APhoto support staff couldn't find anything in the keyboard shortcuts either. It's not us users, it's the misleading design of the software.
https://forum.affinity.serif.com/index.php?/topic/68413-preferences-window-ui-is-frustratingly-designed/
This is another of the many basics that seriously under-staffed Serif hopes to get to someday. At present they seem fully engaged in fixing the horrific bugs that appeared on day 1 of the release of Ver 1.8. We can hope they are also developing a more robust beta testing protocol.
If you let this get to you, you'll understand why PCMag.com describes Affinity Photo as miles behind the programs provided by the company that shall not be named.
On the other hand, I keep using APhoto because APhoto has very powerful features and because I think APhoto's emphasis on non-destructive editing is the correct model to follow. The makers of other editors I own keep sending me links to tutorials that involve destructive editing for the simplest adjustments. I certainly don't recommend APhoto for the average photo hobbyist who is not especially computer literate and who does not enjoy wrestling with technical issues.
 

You need to have the text style applied before you can update it that way, Mike.
So:
Assign the text style to the text. Update the text's style. Then right-click the text style in the Text Styles panel (or click its hamburger menu), and then click Update. Or, for a simpler version of step 3, click the "Update Paragraph Style" icon in the Context Toolbar.

The one you want to update.
Maybe you've found a difference between Mac and Windows. If so, it's probably a bug.
Or, maybe you've found a difference between an older version of Publisher and the current version of Publisher. What version was the presenter using? What version are you using?
What course are you taking?

Dan C.: Thanks for the explanation. Permit me to suggest an idea I'm stealing from Capture One. (Thanks also to Granddaddy for your reply.)
Coding an improved Search feature probably means a lot of work. But perhaps this requires less work: In the keyboard-shortcuts dialog, add a 'save' button to make a file with a table or list of all commands that can be bound to keystrokes[*]. Include whatever shortcuts are already bound to commands. The program then launches the system default browser and displays the temporary file, which will be easy to search within the browser. The same output filename can be used each time to avoid a buildup of temporary files. Each execution of the 'save' command overwrites the previous such file.
Or — save the collection of commands + keyboard shortcuts as a PDF file, then launch the system's default PDF viewer (if none, then in a browser).
Or — have the program save the information in an .afpub file, then open the it as a new document within Affinity Publisher itself (as before—use the same output filename repeatedly).
In short: a solution that could be useful until there's a better Search feature. Then again, a save-list-of-commands-and-shortcuts-to-file feature would be useful as a permanent addition to the program.
___
*  The frosting on the cake: Provide an option to organize the output by menu –or– to list the commands alphabetically within the output file.

Hi MikeA
Unfortunately the Preferences search doesn't currently include searching for Shortcuts, this has been raised previously and is something we hope to change in a future update.
This is certainly confusing, but I can explain why it's happening. When searching in the Preferences search box, you're searching through all of the names of the various settings, so for example when searching for 'tool' the search returns the following results -

Once you add the 's' to tools, there's no longer any sub preferences (in bold down the left side of the dialog) that match the word, hence 'tools' is no longer highlighted.
I do agree this is confusing and could certainly do with improvement, this is logged with our developers as a function of the app that needs further revision, so it will hopefully be address in the future.
I hope this clears things up!

I see posts about this problem fairly often in the Capture One group on Facebook. If you're using Windows and if you're using its built-in image viewer, you're examining your images in a non-color-managed program. For an image viewer on Windows I use the freeware called Irfanview (irfanview.com), which is color-managed. I liked the program enough that I registered it even though I'm not using it for commercial purposes—I'm in and out of that program scores of times each week. If you download it, I recommend also downloading and installing its (free) extensions package.
And if you're not using these programs on a Windows machine, apologies for the unnecessary reply and feel free to use this comment for wrapping fish.

That's a part of Snapping.
Are you sure you have the same Snapping options enabled as the presenter in your tutorial?
In any case, snapping to all 4 edges of the columns works fine for me. Here are the snapping options I have enabled: