Jump to content


  • Content Count

  • Joined

  • Last visited

About lukejanicke

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yes. But for now it only works that way as an initialiser. You can’t change those style decisions and re-apply them across the document. Re-applying Master Pages to child Pages will reset the style AND content of text frames that are defined on the Master Page. I only lost 20 minutes of work before I discovered this the hard way, and I won’t make that mistake again. Patrick, that’s great to hear. In the meantime, I think I can work with Master Pages and Text Styles to get the end product I want.
  2. The help files are pretty clear now. Master Pages are meant for design elements that are common across pages, and not for designing template-like placeholders for controlling styles across different Pages’ content. They’re not like Master Slides in PowerPoint. I don’t have any experience with Adobe ID or other publishing applications (unless you count Word), but it definitely seems like the original intention was there.
  3. Oh dear. Came looking for how to apply new styles from Master Pages without replacing content on Pages. It looks like the Symbols Panel is gone completely. It shows up in Designer Persona, but not in Publisher Persona. Can anyone confirm?
  4. Came looking for an answer for this, and then stumbled on the answer by accident. Tap the top right icon to hide the UI twice quickly. The context menu hides with the rest of the UI.
  5. I just noticed that the Vector Brush Tool uses the stroke color or the fill color depending on which is selected on the colour panel. If the fill colour is selected, then the Vector Brush Tool uses that color, even if you change the stroke color from the context menu at the bottom of the screen. This is unexpected behaviour. The Vector Brush Tool should always use the stroke colour, right? In this screenshot, the top line was drawn with the the green fill colour selected. The second line was drawn with a red stroke color selected. The third line was drawn after changing the stroke color to yellow from the context menu but then also selecting the green fill colour from the color panel. The colours should be (from top to bottom): red, red, yellow. At least the behaviour is predictable so it’s easy to work around. I’m using Affinity Designer for iPad on an iPad Pro 11" with iPadOS 13 public beta 6. I’ve only just started using Affinity Designer, so I’m not sure whether iPadOS beta is part of the problem.
  6. What I do... Use a rectangle with no colour for line or fill. Group it with the elements you want sliced. Make slice from the group. Export. Unfortunately, I don’t think this will help if you have stuff that span across your intended slices.
  7. Solved! I should have noticed that ratio. I thought I had tried changing DPI but then I noticed that even if the document’s DPI is set to 96, the SVG export DPI is automatically set to 72 at first. When I set the document DPI to 96 and also set the SVG export DPI to 96, then the text in the exported image is 12pt/16px on the webpage, same size at the HTML 12py/16px text. Thanks!
  8. Last post on this issue and then I’ll wait to see what others think. My interim solution is to use size 16 pt font in Affinity Designer. It will export as 16 px, which matches the HTML where it will be embedded.
  9. When I change the Document Units in Document Setup… from from pixels to points, 400px by 300px becomes 400pt by 300pt automatically. But the image doesn’t get bigger or smaller, which supports the conclusion that 12pt and 12px are the same in Affinity when exporting to SVG.
  10. When I manually change 12px in the exported SVG file to 12pt, the text in the SVG is displayed bigger than originally designed in Affinity. This will be a problem for designing figures.
  11. I notice that 12pt in CSS is reported at 16px in Developer Tools (in Safari). That seems relevant.
  12. I tested PDF and Affinity Designer exports 12 pt to the same size as a Word document does to PDF.
  13. Okay, so I just noticed that the exported SVG gets font-size:12px, and I think that should be 12 point not 12 pixels. Does this mean that when you choose 12 pt in Affinity Designer, you’re really choosing 12 px?
  14. I am aiming to export SVG files with 12 point text (in Affinity) where that text is the same size as the 12 point text in the HTML where the SVG is embedded. As you can see, the text in the SVG and PNG is smaller that the text in the HTML above it. The HTML <!DOCTYPE html> <html lang="en" dir="ltr"> <head> <meta charset="utf-8"> <title>Test</title> <style media="screen"> * { font-size: 12pt; font-family: "Open Sans"; } </style> </head> <body> <p>This is a test of SVG sizes from Affinity Designer.</p> <p>The font on this page is 12 point Open Sans Regular.</p> <p><strong>SVG</strong></p> <p><object type="image/svg+xml" data="1.svg">Your browser does not support SVG.</object></p> <p><strong>PNG</strong></p> <p><img src="1.png" alt=""></p> </body> </html> The SVG <?xml version="1.0" encoding="UTF-8" standalone="no"?> <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> <svg width="400px" height="300px" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" xmlns:serif="http://www.serif.com/" style="fill-rule:evenodd;clip-rule:evenodd;stroke-linejoin:round;stroke-miterlimit:1.41421;"> <rect x="0" y="0" width="400" height="300" style="fill:#f2f2f2;"/> <text x="10px" y="19.117px" style="font-family:'OpenSans-Regular', 'Open Sans', sans-serif;font-size:12px;">This is 12 point Open Sans Regular.</text> <text x="62.674px" y="162.808px" style="font-family:'OpenSans-Bold', 'Open Sans', sans-serif;font-weight:700;font-size:52.831px;fill:#fff;">400×300px</text> </svg>
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.