Jump to content

Annabella_K

Members
  • Content Count

    35
  • Joined

  • Last visited

About Annabella_K

  • Rank
    Member

Recent Profile Visitors

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

  1. Thanks @thomaso but that workflow doesn't apply to my problem. The answer would be global layers. ☹️
  2. @thomaso I'm not sure you understood what I wrote. My point was that, at least at first sight, their way of master pages and global layers don't seem compatible, so it would be hard to implement. Because let's say you have a master page that has objects using those 3 global layers you have in your example. In Affinity that master page can be added to the page like a layer, but the problem is, you can't just add it to ONE of those layers. That's why I wrote, that you could only add a master page to a global layer, if its every object is on the same layer, more like in a group. At least I think you can't have objects of a group on different layers. Exactly the hierarchy problem you wrote. Objects on the layer are children of the page (parent). Then a page (master or not) can't be a child at the same time. Only way I can imagine it to work is if master pages are not treated as layers, but then it's a fundamental difference. It seems complicated. Sorry if my English is hard to understand, I'm not a native speaker, and also pretty tired. πŸ˜…
  3. Thanks for the explanation @thomaso I couldn't imagine how global layers work. But now I checked out Scribus too, and I think I understand the concept. Just thinking out loud, but I'm not sure if it is compatible in this way with Affinity's approach of mater pages. If I understand correctly, with global layers, you put every page element on a Global Layer, regardless that it's on a single page or a master page. But in Affinity, master pages are like layers on a page: you can stack multiple master pages on a page, change order, etc. So at the same time, you would need to place the master page on a layer, where elements of the master page, are maybe placed on a different layer. It sounds problematic to me unless you CAN'T put master page elements on separate layers. Then they'll always be on the same layer as the master page. But maybe the stackable master pages were their way of implementing global layers (kind of) in the first place πŸ€” I'd like to hear their take on this. Luckily I'm not used to a different approach, and so far this master page way was enough for me, it can be pretty powerful too, IMO. I only wish they would stay "global" also on PDF export. But I can see how this master page approach is not enough for the language changing problem, for example. It would only work with one-click if you had the same layout on every page. And that's hardly the case.
  4. I think it makes sense to have per page Layers too. But there should be global layers. Though I think what I miss about global layers is different from what people mentioned in this thread before. When I export to PDF, I just don't want to have the same layer from a Master page 200 times in the document. I want to switch them on/off with one click - I mean in the PDF viewer too. @keith s could you tell me a practical example of the global layer use you mentioned? I'm relatively new to DTP software and all I know is master pages, I use the method @walt.farrell mentioned above for everything. Though sometimes the logistics need a lot of thinking.
  5. Oh, I was looking for the same thing in Publisher, but I guess it's the same there ☹️
  6. I noticed that despite having Transparent background unchecked in Publisher, the PDF I export behaves like it had a transparent background. Namely, antialiasing shows up as a grey border around shapes. Unfortunately, it also prints that way. Adding a white background manually solves the issue, but I don't know if that's the right way to go, as it adds to the file size. I also tried using the Force pixel alignment option, but sometimes that just isn't enough to prevent this. And when the drawing unit itself isn't pixel, then it gets confusing too. What are some best practices for this antialiasing problem? In some cases I just can't avoid rasterizing things. Thanks in advance.
  7. Thank you again, Walt, I see you here a lot. πŸ˜€ Yes, that's my problem, I can't try it either. Actually there's a simple workaround for that. At least when the symbol is a group, you can copy--paste the elements of the group not the group itself, then they'll be detached. I agree that without the Symbols studio it is limited, but most times I don't use symbols in a complicated way. For example when I make my weekly planner, I make the daily sections symbols, so I can see the design changes on the whole week at once. Detaching and pause-syncing may not be even needed features for this. But being those elements linked to each other is still useful for later editing. Interesting, the first tutorials I found about symbols, the Symbols studio was in Publisher, I was disappointed when I didn't find it there. I had to buy Designer almost solely for this feature. For drawing (just simple things&icons) I still prefer Inkscape, for multiple reasons. But at least it's easy enough to copy paste the drawings from there πŸ˜€ And the exporter is awesome in Designer.
  8. I see that when I create a Symbol in Publisher through the Designer persona, I can edit that symbol later straight in Publisher, without switching to Designer persona. I was wondering, if the symbols are used in a Publisher template for example, then someone, who doesn't have Designer at all, can see / edit those symbols. Or will they be detached?
  9. I'm not sure people got it, but the only reason I brought up InDesign is to show that Adobe incorporated form tools in their publishing software too. But if it's not that good, then that's just more opportunity for Affinity to create a solution that beats Adobe πŸ˜„ I'm using PDFill for now to make the forms, I like that you can import the fields from another project too (though I may found a bug there with calculated fields). Overall it's not bad, but I could imagine better user experience. And I like how at Affinity they think outside of the box, so I really hope they will make this 🀞
  10. Any news about this? I'm still having this issue in all apps (Photo 1.8.2.620, Designer 1.8.3.641 and Publisher 1.8.3.641, on Windows 10). Very annoying.
  11. It would be useful to be able to name the hyperlinks in the properties panel when creating them. When you make documents that contain a lot of hyperlinked objects, it can get hard to find the new one in the list to rename it from "Hyperlink X" to something meaningful.
  12. Thank you ☺️ And there's Go to Source too, perfect πŸ˜€
  13. In Word there's the option to CTRL+click the hyperlinks in the document to open up the URL/jump to the target. Can I do this in Affinity Publisher too? I'd like to check if all the hyperlinks are correct without exporting to PDF first. Thanks in advance.
×
×
  • 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.