[1.8.0.499] Find & Replace and Context Toolbar not finding Character Styles inside a Paragraph Style

[Old Bruce]

I have a Paragraph Style (Chapter Head) which uses the Initial words feature and I have a Character Style set up for that. The only thing in the Character Style (Initial Words Chap Head) which is different is the font's size, 12 points instead of the 14 points for the Paragraph Style.
When I have this paragraph style applied the Find and Replace won't find the 12 point text in the Chapter Heads. The Context Toolbar will also not show the size of the type when there is text selected. Even if I change the font family to something which is unique to the document I cannot see that it is in the document using Finda and replace or selecting the words in the Chapter Head which are a different font family and looking at the Context Toolbar.

[walt.farrell]

I think I understand what you're saying about Find and Replace, Bruce. But can you provide a screenshot to clarify what you mean with " The Context Toolbar will also not show the size of the type when there is text selected." And perhaps provide a small sample document?

[Old Bruce]

13 minutes ago, walt.farrell said:

I think I understand what you're saying about Find and Replace, Bruce. But can you provide a screenshot to clarify what you mean with " The Context Toolbar will also not show the size of the type when there is text selected." And perhaps provide a small sample document?

This is 12 point selected.

Chaps 001 4.afpub

[walt.farrell]

Thanks, Bruce. That's what I thought you might mean, and with your document I see the same thing in the Windows beta.

There is something else odd going on, by the way. Here's a screenshot:

Note that you have two layers named "Text Right". The highlighted one is for the chapter title; the other one is for the text.

Next, it appears that both have the same text content, (CHAPTER 1<pilcrow> Loomings ...). But in fact, the highlighted layer (shown selected on the left) has only the chapter title as the content. And if you "edit detached" and hide that layer, only the chapter title disappears.

However, if you delete that highlighted layer (which contains only the title), all of the chapter text disappears, leaving only the chapter title which moves down and to the left.

[Old Bruce]

40 minutes ago, walt.farrell said:

Note that you have two layers named "Text Right". The highlighted one is for the chapter title; the other one is for the text.

Next, it appears that both have the same text content, (CHAPTER 1<pilcrow> Loomings ...). But in fact, the highlighted layer (shown selected on the left) has only the chapter title as the content. And if you "edit detached" and hide that layer, only the chapter title disappears.

However, if you delete that highlighted layer (which contains only the title), all of the chapter text disappears, leaving only the chapter title which moves down and to the left.

I have two layers on that page. A one Column Text Frame linked to the Two Column text frame. I should have included more pages, most are two columns, only the Chapter start/first pages are like that.

[walt.farrell]

Just now, Old Bruce said:

I have two layers on that page. A one Column Text Frame linked to the Two Column text frame. I should have included more pages, most are two columns, only the Chapter start/first pages are like that.

Yes, I understand that. But it does not explain why deleting the layer/frame that contains the chapter title instead deletes the chapter text and moves the title down.

[Old Bruce]

5 minutes ago, walt.farrell said:

Yes, I understand that. But it does not explain why deleting the layer/frame that contains the chapter title instead deletes the chapter text and moves the title down.

It is one text object, starts with Chapter 1 and continues on from there (Walt; you more than likely know and understand that, it is for people following along). 

Check out the Paragraph styles Chapter Head and First Paragraph. Look at the options I have set for Flow. The head and the first paragraph will not be in the same frame.

[walt.farrell]

1 hour ago, Old Bruce said:

It is one text object, starts with Chapter 1 and continues on from there (Walt; you more than likely know and understand that, it is for people following along). 

Check out the Paragraph styles Chapter Head and First Paragraph. Look at the options I have set for Flow. The head and the first paragraph will not be in the same frame.

Ah. Thanks, Bruce. That explains what I was seeing.

And leaves us with just your issue with the font size not showing accurately.

[A_B_C]

Somehow the initial words seem to be enclosed in a little container of their own that cannot be accessed by the context toolbar readouts (they seem to always read out the font size of the non-initial text) and by Find & Replace. Mysterious. 

[Patrick Connor]

Sorry.

Thank you for reporting a problem using the pre 1.8.0 beta builds. It appears that a member of the Affinity QA team didn't get round to fully investigating this specific report posted in the bugs forums. We are very sorry for this oversight. Yours is one of a number of reports that I am posting this apology to, using an automated script. 

Now we have released 1.8.3 on all platforms containing many hundreds of bug fixes, and we hope your problem has already been fully addressed. If you still have this problem in the 1.8.3 release build, then the QA team would really appreciate you reporting again it in the relevant Bugs forum.

• Report a Bug in Affinity Designer
• Report a Bug in Affinity Photo
• Report a Bug in Affinity Publisher

Each of those links above contains instructions how best to report a bug to us. If that is what you already did in this thread just copy paste your original report into a new thread. We appreciate all the information that you have including sample files and screen shots to help us replicate your problem.

This thread has now been locked as the QA team are not following the threads to which this automatic reply is made, which is why we would appreciate a new bug report if you are still have this problem in the release build.