Chris Christner
Members-
Posts
77 -
Joined
-
Last visited
Everything posted by Chris Christner
-
The workaround on a Mac is to select the template files that have custom extensions and do a get info, then click the "Stationary Pad" button. Opening the docs will create a new file with all the content of the template but the template can't be overwritten. Don't know if Windows has a similar setting.
-
I understand that each Affinity app can save a template file with a .aftemplate extension, and that the templates can be opened in any of the suite applications. But to avoid confusion, why not give each app a unique template extension so it'll open in the correct application? Then if you want to open a Publisher template in Designer, you can simply open it from inside Designer.
-
The problems I have with that are: there's no way to set the B&N tabstop by eye (which is how I like to work) and I don't see why B&N can't just work with the text ruler tabstop. Where's the advantage to it being a specific setting? As a workaround, the tabstop could be set by eye or clicking on it could bring up a field for entering the precise position. Anyway, I thought it was a bug, but it turns out they like it that way. So I'll adapt.
-
As shown in the attached image, I created a bullet style and adjusted the tab stop to where I was satisfied. But the first line of text kept indenting to what I later learned was the tabstop setting in the Bullets and Numbering panel of Paragraph. Am I missing something subtle or is it a bug? Because it seems like the B&N tabstop should be the same as what I set with the ruler tabstop.
-
I didn't know that's how it works. Thanks for the explanation. Part of the problem is that the App store is so flaky. You download software and pay for the pro version. Next time you download it you get the basic version, so you have to click on the buy button, at which point it tells you that you've paid for the pro version and downloads that. That's what threw me, because I expected the store to download the version I'd already bought, not realizing I must have bought it at Serif's store. Anyway, they're giving me a refund, so all's well that ends better.
-
Well, thanks again. That does seem like an incredible blindspot in Publisher, especially since the other major apps (InDesign, Quark, Word, etc.) handle this sort of formatting without making users break out manuals and trusting to luck that the font they've been using can do subscripting. I trust Affinity has addressing this feature on a roadmap so eventually it'll work as expected.
-
I figured out a workaround: Delete a few characters near where the L SEP or P SEP characters appear; save the change; then retype the deleted text. It works! Apparently deleting those characters also gets the unicode characters too. Incredibly time consuming, but at least I can check Microsoft Edge to verify that the text is clean. Please fix this problem ASAP!