Publisher 2 Resource manager updates links even if in settings it uncheked

[anto]

Resource manager updates links, even if in settings it uncheked. Windows 10

[walt.farrell]

10 minutes ago, anto said:

Resource manager updates links, even if in settings it uncheked. Windows 10

Please provide more details on your workflow when this happened.

For me, Publisher 2 detects the file was modified, and provides the toast message warning me of that, but the Linked file is not updated.

[anto]

The same thing with beta 2.2

There is no warning message even.

 

 

[walt.farrell]

Thanks for the added details. It is helpful to know that you're talking about modifying images within Publisher itself and not via some external application.

With that information, I see the same thing happening (image is updated), though I did get a warning:

If I modify the image truly by an external application, I get the warning but the update is not automatic. So it is an issue of modifications that happen only within the application itself.

[NathanC]

Hi @anto,

In your example workflow you're editing and saving the image internally within Publisher app, the setting only affects resources that have been modified externally. For example, if you were to open that same linked image in the AFPhoto app, make a change and then save the image it shouldn't auto update within Publisher because the image has been modified externally.

The current functionality with internally edited resources auto updating with the option unchecked has been logged previously, but was determined as By Design by the developers.

[anto]

1 minute ago, NathanC said:

In your example workflow you're editing and saving the image internally within Publisher app, the setting only affects resources that have been modified externally. For example, if you were to open that same linked image in the AFPhoto app, make a change and then save the image it shouldn't auto update within Publisher because the image has been modified externally.

The current functionality with internally edited resources auto updating with the option unchecked has been raised previously, but was determined as By Design by the developers.

Version 2.0 worked well, and 1.10.x. This is all broken with 2.1

[anto]

If it is as you say, then the Mac version works differently. I was constantly working this way and manually updating the links. I will test it on Mac.

[walt.farrell]

18 minutes ago, NathanC said:

The current functionality with internally edited resources auto updating with the option unchecked has been logged previously, but was determined as By Design by the developers.

I personally have no problem with this update happening automatically, Nathan. However, there's an inconsistency at least in the wording of the Toast message, which says that it was modified "outside the application".

If this is going to be "by design", then they might consider eliminating the Toast when it was really modified within the application itself

[anto]

Here is the video.

 

Mac works completely differently. I prefer the workflow on the Mac, as I can fully control the whole process and know which drawings have been updated and which have not.

[anto]

@walt.farrell Please do not write when you do not work on both systems and do not know the whole truth.

[NathanC]

21 hours ago, anto said:

@walt.farrell Please do not write when you do not work on both systems and do not know the whole truth.

Please be more respectful of other forum users, this is a public forum and other users are entitled to post on your threads. Particularly since you also initially reported this as a Bug on Windows and were originally discussing the problem on Windows.

21 hours ago, anto said:

Here is the video.

 

2023-08-22 о 17.53.37.mov 15.01 MB · 1 download  

Mac works completely differently. I prefer the workflow on the Mac, as I can fully control the whole process and know which drawings have been updated and which have not.

I believe that you've found a workaround to get it the app to not automatically update the resource which only affects MacOS. After making your change if you close the document tab and are prompted to save, the app is interpreting this as an external change and not automatically updating your resource since the option is unchecked. However, if you repeat this again but after making your change if you manually save (CMD + S) and then close the document tab the resource will automatically update, the same as on Windows.

Evidently there is an inconsistency in behaviour here between platforms which i'll get logged with the developers, however since the aforementioned issue with resources updated within Publisher always updating regardless of the setting was considered as by Design by Dev/QA, it's likely that this inconsistency on Mac will be brought in line with Window's behaviour.

 

21 hours ago, walt.farrell said:

I personally have no problem with this update happening automatically, Nathan. However, there's an inconsistency at least in the wording of the Toast message, which says that it was modified "outside the application".

If this is going to be "by design", then they might consider eliminating the Toast when it was really modified within the application itself

Thanks for raising this, the notification/toast message wording is misleading since it's being modified inside the app, so i'll also log this.

[anto]

6 годин тому NathanC сказав:

I believe that you've found a workaround to get it the app to not automatically update the resource which only affects MacOS. After making your change if you close the document tab and are prompted to save, the app is interpreting this as an external change and not automatically updating your resource since the option is unchecked. However, if you repeat this again but after making your change if you manually save (CMD + S) and then close the document tab the resource will automatically update, the same as on Windows.

Evidently there is an inconsistency in behaviour here between platforms which i'll get logged with the developers, however since the aforementioned issue with resources updated within Publisher always updating regardless of the setting was considered as by Design by Dev/QA, it's likely that this inconsistency on Mac will be brought in line with Window's behaviour.

Aren't Designer Persona or Photo Persona external programs? It seems to me that they are external. Because if I don't install Photo or Designer directly, these Personas won't work. So I think it's a bug on the part of Windows.

From documentation:

"The Designer Persona and Photo Persona come directly from Affinity Designer and Affinity Photo, respectively. As such you need to have one or both apps purchased and installed to take advantage of that Persona. The options are unavailable otherwise."

 

How can it be an internal change?

6 годин тому NathanC сказав:

Please be more respectful of other forum users, this is a public forum and other users are entitled to post on your threads. Particularly since you also initially reported this as a Bug on Windows and were originally discussing the problem on Windows.

I'm tired of reading things when users write without knowing the whole truth and convince me that. I wrote that it was a bug in Windows and I still believe that. But I'm sorry, I have 1.10.6, 2.1.1, 2.2 beta. It's hard to remember what program crashed where, especially when I work on different systems and see differences when others don't, and here I'm proving something. This is not directly related to Walt.

Translated with www.DeepL.com/Translator (free version)

[walt.farrell]

47 minutes ago, anto said:

Aren't Designer Persona or Photo Persona external programs? It seems to me that they are external. Because if I don't install Photo or Designer directly, these Personas won't work. So I think it's a bug on the part of Windows.

You don't need to use the Photo or Designer Persona to see this. You could open the Linked image for editing by clicking on Edit Image in the Publisher Persona, stay in the Publisher Persona, and make changes to the image. For example, add an adjustment, merge, and Save. The same issue will occur.

[anto]

13 minutes ago, walt.farrell said:

You don't need to use the Photo or Designer Persona to see this. You could open the Linked image for editing by clicking on Edit Image in the Publisher Persona, stay in the Publisher Persona, and make changes to the image. For example, add an adjustment, merge, and Save. The same issue will occur.

Besides these, I add things that are not in Publisher, only in Personas. So these are external changes. For example, changing the size or changing the profile.

[walt.farrell]

1 minute ago, anto said:

Besides these, I add things that are not in Personas. So these are external changes. For example, changing the size or changing the profile.

Sorry; I don't understand what you mean by "not in Personas". Everything in Publisher (and the other Affinity applications) is in some Persona.

[anto]

Just now, walt.farrell said:

Sorry; I don't understand what you mean by "not in Personas". Everything in Publisher (and the other Affinity applications) is in some Persona.

You wrote about the Publisher's Persona, and I'm talking about the external Personas - Photo and Designer.

[walt.farrell]

9 minutes ago, anto said:

You wrote about the Publisher's Persona, and I'm talking about the external Personas - Photo and Designer.

Those are still part of Publisher. They are enabled by having the Photo and Designer applications, but if you look at, for example, Windows Task Manager, you will see that you still have only the Publisher application running when you use the Photo or Designer Personas. You do not have the Photo and Designer applications running, or they would show up in Task Manager.

But my point was that the same situation (warning of change, and application of change to the Linked image in the main document) happens even when changes are made solely within the Publisher Persona (at least on Windows). Thus, the application is consistent, on Windows.

[anto]

56 minutes ago, walt.farrell said:

when changes are made solely within the Publisher Persona (at least on Windows). Thus, the application is consistent, on Windows.

Because Publisher is a self-sufficient program. Photo and Designer Personas don't work without Publisher, Photo and Designer which means they can't be an internal process. They are external applications.