Jump to content
You must now use your email address to sign in [click for more info] ×

Search the Community

Showing results for tags 'linked document'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Staff and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.4 New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Member Title

Found 4 results

  1. Hey there, I came across the following question and bug while working on a document today. Initial situation: I want to link a Designer document with several differently named artboards, each containing between two or three layers that I want to show or hide separately while the document is linked in Publisher. I'd like to use the long awaited and now available "Layer Visibility Override" in Publisher. I was very excited to finally see it! Question/Possible minor bug: Why is the order of layers in Publisher reverse compared to the order in Designer? The lowest layer in Designer is shown first in Publisher and vice versa, the first layer in Designer is shown last in Publisher. I can't quite follow this logic and it seems a bit backwards in the most literal sense. (Sorry, the screenshot is meant to be read from right to left, because on the right side is the way I set up the layers first in Designer, before linking them second in Publisher on the left side). Bug (?): There is no other way to describe it than that it simply does not work. In my particular case, I'd like to switch between two layers, ticking one off, ticking one on. And it just doesn't work. Instead of switching between these two layers, a third layer is displayed which should remain invisible because I am not even touching it. Also, I'm not so much interested in workarounds for the problem, I know there are other and cleaner ways to set it up, like I could have opted for additional artboards (as I would eventually do once the client narrows down to one version). However, as there should be Layer Visibility Override in Publisher, I'd want to use it. Please see the clip attached. Perhaps someone can confirm this? Or maybe this issue is already known/reported? Cheers Dennis Layer_Visibility_Override_Bug.mp4
  2. It's actually the method of implementing Smart Object . Since now Affinity have implemented Embedded Document and Linked Document , as long as there is a convenient option to convert layers or groups into a embedded document, the Smart Object feature of PhotoShop can finally have replacement. This will be really convenient feature, please you add it!
  3. When having Master A containing a linked image and a Master B containing Master A, when updating the linked image in the document only Master A gets the updated image. Master B keeps the old image. So all masters containing a master with a linked image don't get updated when we reload the changed linked image in the document. See video. only-first-masterpage-updates.mp4
  4. Want some feedback on whats normal behavior when working with linked docs in Affinity Publisher (Windows). I created a doc that contained playing cards (85 pages) in Publisher uses about (2 GB RAM when open). However to be useful i needed to stitch then together into sheets. So i created a second Publisher doc to do this. Created frames for each card and clicked away. The thing is... Publisher started to use about 8 GB of system RAM (only that file open). Is that normal or could it be a bug?
×
×
  • Create New...

Important Information

Terms of Use | 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.