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

saving edits to linked file in publisher


Recommended Posts

24 minutes ago, R C-R said:

1012258365_Resourcemanager.jpg.8c72c691415152fa8466e72a63d20c78.jpg

Information from MEB was a response to a particular problem of converting Image Layer to Pixel layer. Of course, all linked (afphoto, afdesign, afpub) documents are also displayed in the Resource Manager.

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.4.0.2301
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Link to comment
Share on other sites

58 minutes ago, Pšenda said:

Information from MEB was a response to a particular problem of converting Image Layer to Pixel layer. Of course, all linked (afphoto, afdesign, afpub) documents are also displayed in the Resource Manager.

It's interesting to compare the processing if one switches to the Photo Persona and paints on a Linked image layer vs painting on a Linked .aphoto file.

If one paints onto a Linked image layer (which shows as (Image) in the Layers panel) the layer is simply rasterized before painting on it, and it disappears from the Resource Manager.

If one paints onto a Linked document layer (which shows as (Linked Document) in the layers panel) one gets this interesting message from the Assistant:
image.png.e9bb7c21e225688d9173f38610d0d539.png

And then, in the Layers panel, the (Linked Document) layer has become a kind of Group:
image.png.1e5da39b444d8a7c5e8b9d5a556cf7b7.png

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1

Link to comment
Share on other sites

1 hour ago, Pšenda said:

Information from MEB was a response to a particular problem of converting Image Layer to Pixel layer. Of course, all linked (afphoto, afdesign, afpub) documents are also displayed in the Resource Manager.

To be honest about it, I have never been sure about what the Resource Manager should be showing, what should cause that to change, or what might be a bug or some local problem on my Mac that causes something else to happen instead.

That was all my screenshot was supposed to show. I had intended to include some text to make that clearer but before I could do that some weather related problems became an issue that required my immediate attention, so I just quickly posted the screenshot & moved on to deal with that.

All 3 1.10.8, & all 3 V2.4.1 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
Affinity Photo 
1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

  • 2 years later...

What people actually want is behavior similar to smart objects in photoshop… perhaps publisher would let you expand a linked file to manipulate individual aspects of that file and use the studio link features with the layers. Obviously placing images would need embed, link (not modifiable in publisher), Studio link (modifiable in publisher)

Link to comment
Share on other sites

7 hours ago, FeaturePlease said:

What people actually want is behavior similar to smart objects in photoshop…

Welcome to the Serif Affinity forums.

For the equivalent of smart objects, use embedded, not linked, documents.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • 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.