-
Posts
5,012 -
Joined
-
Last visited
Everything posted by MikeTO
-
Yes, because the panel is refreshed when the cursor position changes. The bug is only with Undo not updating the panels for attributes. I should have written panels because the Context Bar is also not updated. For example, if I set the text style to Body and then override the font family, the Context Bar will show "Body +". If I choose Undo, it will still show "Body +". However, if I override the alignment and then choose Undo, it will change back to "Body". Undoing character attributes is missing a call to refresh the UI like undoing paragraph and object attributes.
-
"Historical Ligatures" (hlig) is named "Historic Ligatures" which isn’t the actual OpenType name. This isn't very important but using Historic implies they were important and not just old.
-
Select text or position the text cursor inside of a word, set any character panel value, and then choose Undo - the panel will refresh properly Position the text cursor before or after a word, set any character panel value, and then choose Undo - the panel will not refresh to reflect what was undone
-
You found a new bug in 2.3. Figure spaces are being shown as zeroes in 2.3 rather than as spaces. This is not specific to the font you're using, it's a general bug. This worked as recently as the 2.2 beta because I included figure space in the table in my manual so it's a fairly recent bug. v1.10 versus v2.3.0:
-
It's really important that you finalize your master pages before duplicating a chapter as the template for the next chapter. If you really need to change a master page and it's too tedious to make the same changes manually to all of your other chapters, your only recourse is to sync the masters (which will duplicate them) and then apply the duplicated master to all of the pages - then delete the original unmodified master from each of those chapters. Cheers
-
That happens because the spaces are being added to the end of the previous line. You're trying to add space in the middle of a paragraph but the spaces you're typing fit onto the end of the previous line so they're moved there. This is the same way every word processor works. If you need to enter space at the start of a line mid-paragraph, you will need to start a new line in the paragraph. Position the text cursor at the end of the previous line and press Shift + Return/Enter. Holding down Shift when pressing Return/Enter will start a new line (insert a line break) without starting a new paragraph. Now you'll be able to type spaces at the start of the next line. Cheers
-
New document bug. Formats are missing A2, A1 and A0.
MikeTO replied to Designer1's topic in V2 Bugs found on Windows
You can add A0, A1, and A2 sizes to the list with about 60 seconds of effort. These are just presets so you can add whatever sizes you like. I recommend doing this in dark mode as the Save Preset As icon is invisible in light mode. -
You need to use the Text Frame panel to set the fill and stroke for the frame instead of for the characters. I found the approach to be confusing, too, the first time I used it. I've written instructions for how to do this in the text frames section of the free Publisher manual I've shared in this forum. The link is in my signature. Cheers
-
I don't know but I bet it's for the same reason that macOS sometimes doesn't show spelling options for underlined words and sometimes doesn't underline misspelled words - Apple's implementation of Hunspell is buggy. It probably worked properly at one time but became unreliable at some point over the years. This is an area where Windows users may be better off because Serif implemented Hunspell on their own rather than relying on the OS.
-
Sorry, I had a typo, I should have written this is the context menu you get when you long press on incorrectly spelled words. With incorrectly spelled words, the context menu has spelling suggestions plus ignore and learn. With correctly spelled words, the context menu offers commands for deselect, cut, copy, paste, link, insert filler text, and convert to field.
-
TOC in Publisher
MikeTO replied to pioneer's topic in Affinity on Desktop Questions (macOS and Windows)
It looks like your TOC text styles have space before or space after defined. Edit the TOC text styles and change those values to 0. If it's not those options, then check the leading value in the TOC text styles. There's also a known bug with generating and updating the TOC in that it "picks up" recently applied formatting. For example, if you italicize a word elsewhere in the document before updating the TOC then the TOC will be italicized when you update it. To avoid this, define all the text attributes in the TOC text styles. To avoid italics being picked up, you'd define the text style as the regular non-italic version of the font. You might also want to read the Text Styles chapter of the free manual I've shared in this forum for Publisher. Good luck -
If you add a guide to a master page, it will be present on every page based on that master page. Use the Pages panel to apply a master page to a document page. You can apply a master page by dragging its thumbnail onto a document page thumbnail or by right-clicking the document page thumbnail and choosing Apply Master. Use View > Show Guides to turn on and off the display of guides. Cheers
-
This is kind of strange if every TOC style now has the font size defined. You might try selecting the TOC frame and choose Edit > Defaults > Revert. I doubt that will fix it but it's worth a try.
- 12 replies
-
- table of contents
- paragraph style
- (and 5 more)
-
The Paste inside Doesn't work properly
MikeTO replied to Mustazy's topic in V2 Bugs found on Windows
I disagree, too, but that's okay, there's more than one way to do things. If I've precisely positioned object A over object B so that it will be clipped in a certain way, I would like to be able to cut object A to the clipboard, click on object B to select it, and then choose Paste Inside. Object A would be moved inside B and clipped the way I want. Your suggestion would centre A over B and force me to drag the object back to where I had already positioned it. Neither of us is wrong, we're just using different terms. Yes, the object is still part of page 1 and not on page 3 from an object hierarchy perspective, but it's positioned over page 3 which is what I was trying to say. -
Publisher-Lay out meshed up when moving single page
MikeTO replied to Kyoge's topic in V2 Bugs found on iPad
FYI this has been reported many times but please keep reporting it, most of us agree it is a serious issue. Serif is aware of it but I can only assume it's a hard one to fix because it's the way spreads were designed. For now, I can only recommend never adding or removing a single page in a facing-pages document. Always add or remove a full spread. If you must add or remove a single page, always re-apply the master page to the spread immediately after adding or removing the page. That will help to some degree. Good luck. -
The Paste inside Doesn't work properly
MikeTO replied to Mustazy's topic in V2 Bugs found on Windows
Your page zoom/scroll may be making you think it never pastes on a different page when pasting inside. This is how Affinity works. The test case is a 1 x 1" rectangle at X:7.5,Y:0" in on the right side of page 1 of a facing pages document copied to the clipboard. The target object is a 1 x 1" rectangle at X:1, Y: 1" on the left or right side, as stated below. It's better to have the rulers off for this exercise as the area of the page under the rulers counts as visible. Page 1, page is fully within the viewport: Select the target rectangle and paste inside - it pastes inside using the page offset so the object isn't visible. Page 1, page is scrolled down so that the top 1" and a bit is not visible - Affinity pastes inside using the original X:7.5" but with Y of 8" plus the 1" and a bit you scrolled down, for a Y of 9.0 something. This happens because Affinity will not paste an object that is fully off screen so it compensates - why it over compensates with this much offset is a mystery to me. Page 1, page is scrolled down so that the top 4" and a bit is not visible - Affinity pastes inside using the original X:7.5" but with a Y of 8" plus the 4" and a bit you scrolled down, for a Y of 12.0 something. Or it would have, but because the page is only 11" tall, Affinity then pastes is on page 3 with a Y of 0.0 something, subtracting 1" for the gap between pages or something like that. If you also shift the page to the right in the viewport, you can get it to paste inside onto page 2 but it's just more of the same. Sorry, I wasn't disagreeing with you, I was just pointing out that the example I was talking about used paste inside, the same would have happened with paste. I fully agree that paste inside doesn't work properly. As I wrote earlier, the way to fix it is: If the copied object overlaps at all with the selected object, paste the copied object inside it without adjusting the X/Y coordinates. Trust that the user positioned the copied object as desired before copying or cutting it and paste it in the same position. If the copied object doesn't overlap with the selected object, paste the copied object inside the selected object while adjusting the X/Y coordinates so that the pasted object is visible inside the selected object. i.e., set the pasted object's offset to 0/0 from the current Transform panel anchor. Doing this would ensure that the pasted inside object is always visible after pasting and is never on the wrong page. -
Have you tried restarting macOS? I know that's basic but you never know. You might also try upgrading to Sonoma 14.2.1 from 14.1 - there was another Print dialog issue in 14.1 that seems to have cleared up with 14.2 so it's worth a try. It might be something with a corrupted print preset so you could try deleting all of your presets. Good luck.
-
I don't really use the afphoto file format so I don't have enough files to perform much of a test. While I avoid placing documents in my afpub files due to potential performance reasons, I hadn't really considered whether they'd consume more memory. As we page through our Publisher documents and come across linked images and documents that we haven't viewed yet this session, Publisher needs to retrieve the image or document and render it at a higher resolution than the low resolution preview stored in the afpub file. If it's just a photo in the afphoto container, i.e., a single pixel layer, the memory required should be about the same as if it were TIFF or PNG, but if the afphoto has a bunch of layers and adjustment layers then Affinity will need to render all of that and it will take more memory than a flat image.
