Jump to content


  • Content Count

  • Joined

  • Last visited

About wesleyb

  • Rank

Profile Information

  • Gender
    Not Telling
  1. Regarding the other symbol issues mentioned: Almost all seem fixed in Affinity Designer 1.8.4 (macOS 10.15.7). The one I can reproduce is https://forum.affinity.serif.com/index.php?/topic/31137-compound-boolean-mode-not-synced-across-symbols/.
  2. Seems fixed. Tested in Affinity Designer 1.8.4 (macOS 10.15.7). P.S. I remember, last weekend, experiencing a similar issue on iPadOS (latest OS, and latest AD version, at the time), but only when working with multiple artboards. If I reproduce and report it, then I would do so in the appropriate forum.
  3. Seems fixed (the original issue, not @Bento's animation). Tested in Affinity Designer 1.8.4 (macOS 10.15.7). --- Regarding I vaguely remember experiencing a similar issue on (1) macOS, several years ago; and (2) iPadOS, when working with multiple artboards, last weekend.
  4. Tested in Affinity Designer 1.8.4 (macOS 10.15.7); the software did not crash.
  5. Seems not fixed, yet—the workaround is still effective. Tested in Affinity Designer 1.8.4 (macOS 10.15.7): Create compound shape Æ from shapes A and E via boolean operation subtract. Create symbol from compound shape Æ. Add second instance of symbol. In first symbol instance, change boolean operation of shape A (from subtract to add). The second instance of symbol is not synced. Via the layers panel, move either compound shape Æ (the one changed or the one not changed) out of its symbol*, and then move it back in to the either symbol instance; the moved compound shape is now synced between both symbols. * (but not into the other symbol instance; which, by the way, is impossible, in this version)
  6. Seems fixed. Tested in Affinity Designer 1.8.4 (macOS 10.15.7); deletion of the linked image is synced across instances of a symbol that was built from a group with the linked image. Unable to test "(in some circumstances)".
  7. Tested in Affinity Designer 1.8.4 (macOS 10.15.7); the symbol links are maintained. I tested symbol links by manipulating each symbol in the duplicated grouped object: changing size of shape in symbol changing color of shape in symbol deleting shape in symbol moving shape in symbol
  8. Seems fixed. Tested in Affinity Designer 1.8.4 (macOS 10.15.7); the "Expected result:" occurs. Regarding the "Interesting side note:", a symbol may not be nested into itself—the symbol simply will not move into itself, when instructed to do so via dragging it via the layers panel.
  9. I add my vote. Forum posts seem like an inefficient means to quantify support. I have also "Liked" the original post. What is the official and effective way to add community support for a feature?
  10. Oh, I just watched a video tutorial for Affinity Publisher about "Linked images". It has exactly the feature I had hoped for, and still would greatly utilize. Are "linked images", as available in the Affinity Publisher Beta, coming to other Affinty products?
  11. I agree that users, and I add that staff, could benefit from a public issue tracking system; but, there are disadvantages for staff (non-technical wall-of-text bug report spam, exposure of sensitive internal communication). I have reated a feature suggestion post that attempts to solve the disadvantages of both sides, and hopefully will promote constructive discussion.
  12. I am using Affinity Designer 1.6.1. In my 2018 follow-up post, I embed the file. The behaviour matches MEB's statement "Affinity Photo and Designer both embed 'the placed' files in the document without any relation with the original external file." I think, when authoring the original post, I "linked" the file, because the verbiage was different many versions ago. I accept this behavior, and have worked with it for years, now. That all said, it would be great to have a living relationship between an embedded document, and the original document that was embedded, so that I could share changes across documents. I imagine that feature, which does not seem to exist in Designer, as cross-document symbols; such a feature could serve, if it worked well, as a replacement for per-document symbols, which are woefully buggy.
  13. Known Situation I am aware of the following: Serif code is not open-source, so direct public access to an internal issue tracking software is not likely. The forum itself is not suitable for bug tracking. The forum is not used as an issue tracker by Serif. A forum, for non-tecnical bug reports, is understandable, because a user may produce a wall of text, that must be parsed, tested, and converted into a technical bug report. Request / Suggestion Provide the users access to a pre-filtered view of the issue tracking. I.e. users would be permitted some or all of the the following: see list of issues see platform of issue see related milestone see kind of issue (feature, bug, defect) see status of issue (in progress, queued, backlog, pending review) see date of last activity on issue subscribe to activity But, users would not be permitted the following: view internal communication about issue comment on bug Benefits Managing forum posts, that discuss the same bug, could then be as simple as linking to a single bug report. Answering new forum posts, that ask about the status of an old known bug, could be as simple as linking to a single bug report. Users can be informed clearly of known and unknown bugs, thus reducing requests or losing loyalty due to abandonment. Status update posts, of project milestones, could be made with less effort.
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. 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.