APublisher "forgets" about hidden layers

[joe_l]

1. Create a document in APu.

2. Place an ADesigner file (linked) having several Layers (with a big L).

3. Hide one of the Layers in APu.

4. Save the APu document.

5. Open it again.

Result: The hidden Layer is shown although the Layers pulldown says it is not. So you have to show this Layer and hide it again.

When the AD file is embedded, this is working as expected. HWA on or off does not make a difference.

[Old Bruce]

9 hours ago, joe_l said:

1. Create a document in APu.

2. Place an ADesigner file (linked) having several Layers (with a big L).

3. Hide one of the Layers in APu.

4. Save the APu document.

5. Open it again..

When you do step 3 are you prompted to save the Designer file? Here on Mac what happens is I Double click the Placed Designer file and it opens in a new window/tab. I hide the Layer layer and close the Designer file window/tab which results in a Do I want to save the changes dialog. 

It seems strange that you are not being prompted to save the linked Designer document after doing an edit.

[joe_l]

13 hours ago, Old Bruce said:

It seems strange that you are not being prompted to save the linked Designer document after doing an edit.

No, I am not prompted to save and I do not find this strange. This is how it works e.g. in Indesign with PSD files with several layers. Hiding the layer in APu and therefore being forced to save the AD file would destroy the benefit of the feature of hiding / showing layers in APu IMHO. Imagine a graphic with several different backgrounds in the AD / AP file or slight variations in this file. Just hide / show these layers in APu is extremely useful, at least for my workflow.

Hmm. To clarify: I do not double click the AD file, I just use the Layers pulldown in APu.

[NathanC]

Hi @joe_l,

Can confirm i've replicated this layer state syncing issue and logged it with the developers.

[Affinity Info Bot]

The issue "Linked Resources- Layer visibility states are not synced when file is re-opened" (REF: AF-6647) has been fixed by the developers in the latest beta build (2.6.4.3439). The fix is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us.