Jump to content


  • Content count

  • Joined

  • Last visited

Everything posted by hbeier

  1. Hello! I have noticed the file size of an afpub keeps increasing indefinitely if it has an afdesign or afphoto document linked or embedded, even when no changes have been made to the linked document. The first thing I have tried is to turn off Save History With Document, but it was already off. I recorded my screen to demonstrate the issue. In the video, please notice how the file size changes after trivial operations such as moving a rectangle: https://www.dropbox.com/s/y9ilpg67o3fbb7c/afpub filesize increase.mp4?dl=0 I’ve also tested placing a png, in which the case the file size increases in the next 2 saves and then goes back down. I am running Affinity Publisher 1.7.1 on MacOS 10.14.5.
  2. I understand that. The problem is not how the file size jumps from 1MB to 20MB with a linked afdesign file. This is fine. My issue is how every subsequent save will increase the file size by ~400KB even when the only change in the afpub file is the position of a rectangle that is unrelated to the linked file. I used to work in CorelDRAW, so Cmd+S is in my muscle memory and I end up with huge files. This happens with psd as well.
  3. I don‘t think that‘s true. You may test this yourself: 1. Copy some text from Affinity Designer and paste in TextEdit using ⌥⇧⌘V (Paste and Match Style). Nothing will be pasted. This is essentially pasting as plain text. 2. Now paste in TextEdit using ⌘V (the normal Paste). The text will be pasted as rich text. 3. Then, copy the text in TextEdit and paste it back (in TextEdit) using both ⌘V and ⌥⇧⌘V. You will notice they both work fine, as TextEdit sets the clipboard correctly with plain text and rich text versions. Inspecting the clipboard contents from different apps a while back also indicated that Affinity Designer is not copying things correctly. See that the 4th line is missing the title attribute:
  4. I’ve recorded a screencast to hopefully make the issue more clear. In short, Affinity Designer seems to copy text as rich text only. TextEdit can paste it, but Sublime expects the plain text part which is missing from the clipboard. It works if copy in AD, paste in TextEdit, copy in TextEdit and then paste in Sublime Text. Affinity copying and pasting text.mov
  5. I believe everybody was focused on the iPad app for the last few months (congrats on that!), so here is a quick bump so you don't forget about us. This bug has been around for almost 2 years and is increasingly annoying to deal with. I've shared the steps to reproduce it here: Cheers!
  6. I'm working on some files stored on pCloud Drive. Sometimes, when I try to save the file, I get this message: This probably happens because pCloud is uploading the file to their servers at that time. However, as soon as I click OK, the file closes. I do not get a chance to save it somewhere else and I lose all the changes I've made. Please look into this "file must now be closed" policy.
  7. I am also experiencing this bug for a couple of years now so I've decided to inspect this issue using some clipboard tools. I may be wrong here, but it seems the clipboard contents when copied from Affinity are missing the title attribute. This was using the text tool with some highlighted text.
  8. Unfortunately, not fixed yet as of Designer 1.6.1 and Photo 1.6.7.
  9. hbeier

    Text opacity bug

    The same color is applied to a vector object (rectangle, line, etc) and a text object. When their opacities are not 100% and they are placed over a non-white background, their colors get rendered differently. See the image below and the attached file. Text opacity bug.afdesign
  10. hbeier

    Text opacity bug

    Ah, that makes sense! I wasn't aware of that setting. Thanks for looking it up and letting me know!
  11. Another option would be to show the error message but not close the file. In this scenario, Affinity would keep the file open in the [Modified] state, granting us the ability to Save As... This is similar to how other programs handle this. I know that Adobe Illustrator and Sublime Text work this way. Having said that, I'm aware they are not sandboxed apps and are allowed to do many things Affinity apps are not. I understand your position. However, I'd like to argue our suggestions would make the apps more reliable and would probably save you from some angry customers in the future.
  12. The workaround I've found is to only work with files located in synced folders (using the pCloud Sync feature). I'm guessing it has something to do with how pCloud upload files to their servers. I've also found that Illustrator is not imune to this. However, instead of immediately closing the file, it simply recuses to save it and gives me a chance to save it somewhere else. I've been meaning to open a support ticket with pCloud to discuss this, but I am kind of swamped with work and couldn't find the time to do it.
  13. Yes, that flattens all adjustments and creates a pixel layer. However, I still have to manually sample the result with the Color Picker tool, which can become a burden when I have multiple gradients. It would be better if Affinity Designer could do this for me while keeping my vectors intact, something similar to Illustrator's Recolor Artwork.
  14. I know this is an old thread, but I'd like to express my vote for this feature as well. Adjustment layers on Affinity Designer are nice, but we can only merge them with pixel layers. I miss the ability to merge them with any kind of layer (text, curve, etc) so I can reuse the new colors elsewhere in a much more direct way and without cluttering my files with a bunch of identical adjustment layers.
  15. This bug has been around for a while now: https://forum.affinity.serif.com/index.php?/topic/26366-ad-151-mac-problem-with-the-view-hand-tool-spacebar-shortcut/?p=142192 Any chance of getting this fixed on 1.6? It is getting increasingly annoying to work around it.
  16. I have been able to reproduce this consistently with the following steps: 1. Hold down spacebar. 2. Click and drag with the hand tool (but don't release the mouse button). 3. Release the spacebar. 4. Release the mouse button. In a nutshell, if I release the spacebar before the mouse button I'm stuck with the hand tool until I press the spacebar again.
  17. This bug seems to be related to the Assets panel indeed. Even if I close it, I can’t move objects around where the panel was. Check out the attached video. Assets panel bug.mov
  18. The language dropdown of my Character panel only shows English, Portuguese and Spanish. Is there a way to add more languages to it? For me, this is not about spelling, but language features that are built into OpenType fonts. (I’m a type designer and I use Affinity Designer to make the promotional images for my fonts, btw.) For example, this is some of the OpenType code that is present in the locl feature of my fonts. These substitutions only happen when the language of the text is set to Dutch, Catalan and Romanian, respectively. If the glyph doesn’t have a Unicode assigned (which is the case of iacute_j.loclNLD), there is no way for me to input it into AD. And while we’re here, any chance on getting a Glyphs panel?
  19. Following up in this topic, I’ve found out Affinity Designer doesn’t honour the locl OpenType feature. This is how it behaves in Adobe apps:
  20. Ok, I’ve found out there is a way to add more languages to it. AD populates that dropdown according to the languages I’ve checked on the spelling options of System Preferences. While I see the reason for this, it would be nice to have more languages available by default without requiring me to change my global spelling options.
  21. hbeier

    Pen tool behavior

    I believe it is best to seek inspiration for the Pen Tool on type design software. Granted, I use them for a living, but I really would like to see some of these features in AD: spacebar while putting down an anchor to reposition it, moving anchors while keeping off-curve handles in place, being able to constrain handles to right angles afterwards (shift key will only constrain to the original angle). Take a look at this short video from Glyphs: Maybe download its trial and use it for a while. It is fantastic!
  22. First of all, congratulations on this huuuuge update! I’m almost ditching Adobe apps completely... I see you reworked the Typography window, adding previews and displaying the applicable options only, which I appreciate. However, I’ve noticed an issue with Case Sensitive Forms and Capital Spacing on the latest stable version (1.4). I can no longer access these features after I’ve typed some text. Here are steps to reproduce it: 1. Select the Artistic Text Tool and click anywhere on canvas. 2. Notice the options to apply CSF and CS are there: 3. Type anything. 4. Notice the CSF and CS options are no longer there: In time, there is a small cosmetic issue. While most UI text are set to the system default (San Francisco), the italics are set in Helvetica, as you can see on the labels for All Caps and Titling on the screenshots above.
  23. I have a text set on Helvetica Neue Thin. When I hit cmd+I or press the italic button on the toolbar, the typeface changes to Helvetica Neue Light Italic. The same thing happens on other type families and for the Book weight, which changes to (Regular) Italic. I'm running AD 1.3.5 on OS X 10.10.5.
  24. Thank you! While you’re at it, it would be nice if the AD sorted the fonts on a family by weight, like InDesign does. I believe they use the fonts’ weightClass parameters for this: http://www.microsoft.com/typography/otspec/os2.htm#wtc
  25. If I apply a 3 step gradient map to a CMYK image and then edit the CMYK values of said gradient map, Affinity Photo doesn’t apply the exact colors I want. For example, my gradient map needs to have the following values: Position 0%: 0 80 90 0 Position 50% 75 100 0 0 Position 100%: 90 100 0 30 After I set the colors and go back to the color picker (on the gradient map window), the values are: Position 0%: 0 92 98 0 Position 50%: 82 78 0 0 Position 100%: 96 94 0 0 I’m assuming this happens because the gradient map doesn’t use the CMYK color space natively. Am I correct?