Failed to transfer file

[MickRose]

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.

T-shirts - generic.afdesign

[Dan C]

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?

[MickRose]

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.

[walt.farrell]

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/

 

[Dan C]

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

[carl123]

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 😄

[Dan C]

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