Jump to content

Recommended Posts

I have an Af Designer file which will open in Publisher okay, but when I am in Designer and use the File/Edit in Publisher command I get this message. I don't know if this a bug or something to do with the file. I'm using 471 on both. The file is attached in case anyone want to try.

image.png.86ccb7697a1d3b31a52bc6ad1a1eb025.png

T-shirts - generic.afdesign

Windows 10 Pro, I5 3.3G PC 16G RAM

Link to comment
Share on other sites

Hi MickRose :)

I've opened your .afdesign file in Designer, then used File>Open in Publisher - at which point Publisher launched (as it wasn't already running) and the file was transferred as expected.

Could you please try moving the location of the file you're trying to edit in Publisher - I'd recommend the desktop - then open this file again in Designer and try sending it to Publisher. Does the file open correctly now?

Link to comment
Share on other sites

  • 1 year later...
On 8/19/2019 at 7:34 AM, MickRose said:

Hi Dan C - I think I know what's caused this problem. the file I opened was Read Only (I use it as a template). When I changed that property it transfered fine.

I just accidentally reproduced this :)

@Dan C: Is that logged as a problem? I don't see why one shouldn't be able to use File > Edit in ... with a Read-Only file.

Note: This recently came up in a different context: https://forum.affinity.serif.com/index.php?/topic/141439-file-lost-when-switching/

 

-- 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.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Link to comment
Share on other sites

16 hours ago, walt.farrell said:

@Dan C: Is that logged as a problem? I don't see why one shouldn't be able to use File > Edit in ... with a Read-Only file.

I can confirm there's nothing directly logged with our developers regarding this currently, as I can see 2 sides to this issue - as a 'Read Only' file cannot be edited, I'm not sure I would expect an 'Edit In' option to work, however one could argue that's being particular with the wording as AFAIK there's no real reason why the file couldn't be transferred in the 'read only' state to a different Affinity app.

I'll get it logged with our developers now, but I suspect it may be regarded a suggestion, rather than explicitly a bug :)

Link to comment
Share on other sites

3 minutes ago, Dan C said:

but I suspect it may be regarded a suggestion, rather than explicitly a bug

It's a bug

3 minutes ago, Dan C said:

as a 'Read Only' file cannot be edited

Read only files can be edited and "Saved as..." to a new file name

If you choose to edit a read only file, with the intention to "Save as..." later on then "Edit In" should allow you to continue your edits.

As it is now any edits you do on a Read Only file are all totally lost if you use the "Edit In" command which is taint amount to the software crashing.

Losing work is never an acceptable situation

 

PS Read only files, also, do not show up in the File > Open Recent files list (Windows 8.1)

That's a bug too 😄

To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.

Link to comment
Share on other sites

Thanks for the clarification Carl!

3 minutes ago, carl123 said:

As it is now any edits you do on a Read Only file are all totally lost if you use the "Edit In" command which is taint amount to the software crashing.

Losing work is never an acceptable situation

I certainly agree and we never wish for users to lose work in Affinity - so I will get this logged as required now.

11 minutes ago, carl123 said:

PS Read only files, also, do not show up in the File > Open Recent files list (Windows 8.1)

That's a bug too 😄

Many thanks for pointing this out, I can replicate this here on Windows 10 and so I'll get this logged also :D

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.