walt.farrell Posted March 26, 2023 Posted March 26, 2023 Recipe: Create a document with a Master Page in Publisher 2 (either 2.0.4, or 2.1.0.1732 Beta). Add an item to the Master Page. I used a Rectangle. Lock the item. Copy the locked item from the Master Page. Paste it somewhere else (on a page in the same document, into another document in T, or another document in Designer, etc.) The pasted item is Locked, and cannot be Unlocked. Late discovery: Even on a page which inherits the item directly from the Master Page, the item cannot be unlocked, even using Edit Detached. It can only be unlocked by editing directly on the Master Page. Note: In V1 (1.10.6) a Locked item from a Master Page always seems to be pasted as Unlocked. That also seems incorrect, so perhaps there was a V1 bug that has been fixed. But now, the item cannot be Unlocked, which also seems wrong (and worse behavior than V1). Sample document: locked-master-page-object.afpub Notes: The rectangle on the Master Page is locked. Page 1 inherits it from Master A. It cannot be unlocked on Page 1, even using Edit Detached. On Page 2, the object has been copied on the Master and Pasted to Page 2. It cannot be unlocked there, either. 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 18.3.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
MikeTO Posted March 26, 2023 Posted March 26, 2023 Same on macOS. Note that the original reverse of copying a locked object from a regular page to a master page still pastes as unlocked. walt.farrell 1 Quote Download a free PDF manual for Affinity Publisher 2.6 Download a quick reference chart for Affinity's Special Characters Affinity 2.6 for macOS Sequoia 15.3, MacBook Pro (M4 Pro) and iPad Air (M2)
Dan C Posted March 27, 2023 Posted March 27, 2023 Hi Walt, Mike, The behaviour is expected within the same document, however I do not believe this should be affecting objects pasted into new documents and have created a bug report for this. Lee Quote
walt.farrell Posted March 27, 2023 Author Posted March 27, 2023 1 hour ago, LeeThorpe said: The behaviour is expected within the same document, however I do not believe this should be affecting objects pasted into new documents and have created a bug report for this. Thanks, Lee. But I'm curious why I should be able to create a locked layer within the same document that cannot be unlocked. What purpose is served by having a layer that cannot be unlocked? 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 18.3.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
smadger Posted April 1, 2023 Posted April 1, 2023 On 3/27/2023 at 11:37 AM, LeeThorpe said: Hi Walt, Mike, The behaviour is expected within the same document, however I do not believe this should be affecting objects pasted into new documents and have created a bug report for this. Lee Just to chime in and add my voice to this as I had the original problem. Regardless of being in the same document or not, I should never be in a situation where I have a layer that cannot be unlocked and edited, and I really don't understand why this behaviour is desired when it state cannot be reversed? This caused me a lot of lost time and frustration. If you're saying that this is intended then I think at the very least there should be a menu option to break layer locking inheritance as a "break glass" scenario. Oufti and walt.farrell 2 Quote
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.