max3.2 Posted December 4, 2022 Share Posted December 4, 2022 Hi, as the title says - whats the best practice here to propagate guides to lower masters. Sample: - Create Master A, add a guide - Create Master B, inherit Master A. Guide is visible dashed (assume this means from Master) - Create Master C. Inherit Master B (which then, as confirmed in the layers panel, contains Master A). Guides are gone. Not even dashed. Is this by design? Is this a setting? I know I can apply multiple Masters so I could apply A and B to C but then, on C, there's A in the main level and A in the sub level, so applied twice. Quote Link to comment Share on other sites More sharing options...
Old Bruce Posted December 4, 2022 Share Posted December 4, 2022 I am not seeing this in Version 2 on Mac OS 11.7.1 I do recall that this happened in version 1. I made the guide and then dragged the Master onto the already made Master Page and then dragged that Master onto the third Master. No use of the context menu's Apply Master... or Apply to Pages... Quote Mac Pro (Late 2013) Mac OS 12.7.6 Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 | Beta versions as they appear. I have never mastered color management, period, so I cannot help with that. Link to comment Share on other sites More sharing options...
walt.farrell Posted December 4, 2022 Share Posted December 4, 2022 1 hour ago, Old Bruce said: I am not seeing this in Version 2 on Mac I'm not seeing it in Publisher 2 on Windows, either. Made guides on Master A. Applied Master A to Master B, and applied Master B to Master C. All 3 show the Guides. ashf 1 Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 17.7, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.7 Link to comment Share on other sites More sharing options...
ashf Posted December 5, 2022 Share Posted December 5, 2022 I confirmed that this has been fixed on Windows before. Quote Link to comment Share on other sites More sharing options...
max3.2 Posted December 5, 2022 Author Share Posted December 5, 2022 Thanks for the quick replies. My bad, this is fixed in V2 but still present in the newest V1.10(.6?). Currently, some issues prevent me from upgrading to V2 so I have to work around that issue I guess. Quote Link to comment Share on other sites More sharing options...
ashf Posted December 6, 2022 Share Posted December 6, 2022 4 hours ago, max3.2 said: Thanks for the quick replies. My bad, this is fixed in V2 but still present in the newest V1.10(.6?). Currently, some issues prevent me from upgrading to V2 so I have to work around that issue I guess. it's not fixed in 1.10.6. fixed in v2 only. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.