Jump to content

Editing linked files - confused result


Recommended Posts

Right now editing linked files is a little confusing - if I place a Designer file in Publisher as linked, and click 'Edit Document' it opens in a new tab and I can choose to edit it in Publisher mode, or with Studio Link switch to Designer mode, switch back to the first tab and the 'linked' file has updated. But if this is a linked file; I think one of two things should have happened at this point:

  1. My linked original Designer document should have been updated as well - if I chose to use linked documents that's because I want any changes I make to take effect in all documents that use that resource.
  2. Failing that, the file should have switched to embedded (with a warning that that would happen if I went ahead and edited)

Instead, though the file is still linked, if I now go back and open the original of the linked file in Designer, it hasn't updated with the changes made in Publisher.

Further, if I go back to the original Designer file and make changes there and save, in the Publisher file, it correctly shows the file as updated in Resource Manager, but if I update from there, there is no warning that 'local' edits to the file (within Publisher) will be discarded.

 

MacBook Pro (15-inch, Mid 2015), macOS 11.0.1 Big Sur
Affinity Designer : 1.8.6 (beta 1.9.0.23)  Affinity Photo: 1.8.6,   Affinity Publisher: 1.8.6 (+ beta 1.9.0.902)

Link to comment
Share on other sites

Yes, that's how it works right now. For editing purposes, Edit Document (used with any file that is not a raster image format) saves the edits only to the embedded copy of a Linked document.

Edit Image (used with raster image files, JPG, TIFF, PNG) will save to the linked original.

Serif have, if I remember correctly, acknowledged this inconsistency, but I don't recall if they've said what they plan to do about it. Perhaps one of the Serif staff query the Developers to find out.

 

-- Walt

   Desktop: new:  Windows 11 Home, version 21H2 (22000.613) 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090  (old: 16GB memory, Intel Core i7-6700K @ 4.00GHz, GeForce GTX 970 )
   Laptop:  Windows 10 Home, version 21H2 (19044.1706) 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Affinity Photo 1.10.5 (.1342) and 1.10.5.1342 Beta   / Affinity Designer 1.10.5 (.1342) and 1.10.5.1342 Beta  / Affinity Publisher 1.10.5 (.1342) and 1.10.5.1282 Beta
 iPad Pro M1, 12.9", iPadOS 15.4.1, Apple Pencil 2, Magic Keyboard

  Affinity Photo 1.10.5 (.280) and 1.10.2 (.266) Beta / Affinity Designer 1.10.5 (.21) and 1.10.3 (.19) Beta 

Link to comment
Share on other sites

  • 4 months later...

Fixed in the latest beta (1.8.502) - :D - nice work Affinity!

MacBook Pro (15-inch, Mid 2015), macOS 11.0.1 Big Sur
Affinity Designer : 1.8.6 (beta 1.9.0.23)  Affinity Photo: 1.8.6,   Affinity Publisher: 1.8.6 (+ beta 1.9.0.902)

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...
 Share

×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. 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.