Jump to content


  • Content count

  • Joined

  • Last visited

About Matthias

  • Rank
    Advanced Member

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Hamburg, Germany
  • Interests
    music, design, communications, human condition

Recent Profile Visitors

600 profile views
  1. Sometimes slices of grouped objects containing open paths are calculated with an unwanted margin, see attached AD file. My guess is that Designer’s export persona calculates (even nonexistent) node handles pointing outside of the bounding box of the group. Any ideas? Slice with unintentional margin.afdesign
  2. Thanks, Matt. You’re the best!
  3. Yeah. If it was a per-element chooseable behaviour (maybe called something like “common/unified/linked location“) and a so-tagged element could be copy-pasted to different pages it could be of use – if it were also possibe to decouple the behaviour from the element at any time should you change your mind. The tagging could even happen just by applying a special "tag-copy” command (like alt-cmd-c) which would paste the element a) with the tagged linking attribute b) at exactly the same location on any given different page. The difference to a master page element would be that other atributes like text content or colour could change per linked element, just the position is linked. Then, maybe this is kind of a special use case.
  4. I tried your recipe, A_B_C, and that’s how it is done. Works with other elements than text frames, too.
  5. Yes, Pauls, I can. Check the linked file and see for yourself. Linked Frame behaviour.afpub
  6. Why not be able to press option anytime while dragging? It should be possible to modify the given action at any time, it‘s a modifier key after all. As a Mac user I am used to this behaviour from macOS Finder. So I still find myself accidentally expecting it in Affinity apps where nothing will happen as long as I haven’t pressed option before I start dragging. I think this is an oversight as it wouldn’t interfere with anything else.
  7. Läppä, I’d opt for your second suggestion: click + drag -> modify the action anytime in the midst of dragging by pressing the modifier key. Why not just do it like macOS Finder does?
  8. It is what it is, isn’t it? Meaning: The developers chose to not (yet) add scripting and I can easily imagine a few reasons why. Like being in total control of the quality of the shipping product since Affinity surely would be blamed for any third party plug-in failure. So I wouldn’t paint a picture in which we are “at the mercy of the developers”. I think the do like their customers a lot and try to give them what they need (like arrowheads). Even when the customers are nagging sometimes, like me.
  9. Yes. It can be deleted. Could be also be deleted before This is how I singled out the bug: By deleting the remnant layer on one page which in consequence didn't crash Publisher anymore while the other pages that still showed this layer kept on crashing it immediately.
  10. Affinity Designer vector output to Apple Motion: I am all for it as well. Even if was an unofficial hack for the time being, an experimental export feature (and labeled as such) it would still be tremendously helpful.
  11. Just checked the most recent beta with my faulty document. The bug seems to be fixed, Publisher does not crash anymore when there’s an abandoned master pager present and you click on an element. The abandoned layer however is still present and still indicated as a master page layer. As long as it doesn’t do any harm to the rest of the file I am fine with it.
  12. Sure they are, Walt. I do not expect the Affinity team to be aware of every petty post, they have work to do and they are doing it greatly. But there is also a huge community of talented fellow designers knowing lots of things I don’t. Hoping to tap into their knowledge is why I bumped on the weekend — just before this post will fade away into the mist of time.
  13. Hi all, I found a bug: One of my documents (stripped-down version attached) causes Publisher to crash immediately as soon as you click on any element (not when you select elements in the layers palette, though). I think I found the culprit: Page 2 shows a second master page layer („Master-Seite“, see screenshot) – but there is only one master (without any content). When the 2nd master page layer is deleted in the layers palette, the file behaves normally again. This behavior begs another question: I don’t know where the 2nd master layer comes from. Maybe I did create it a few months ago and then deleted it. But why is there still this remnant layer with a master page indicator stripe on the left? double-masterpage-bug.afpub