"Apply Layers Overrides" command in Layers pane SOLVED

[rakunavi]

=== UPDATE ===================================================================
The issue reported below has been resolved in Ver 11.0.0.
I appreciate all the hard work and efforts of the support and development team.
==============================================================================

Hello all,

The online help describes the "Apply Layers Overrides" command in the Options menu of the Layers pane as follows.

• Product Manuals » PDF-XChange Editor V10 » Tabs Guide » View Tab » Editing Panes » Layers
  Click Apply Layers Overrides to display all layers. This option includes layers not listed in the Layers pane.
  https://help.pdf-xchange.com/pdfxe10/in ... ne_ed.html

• figure1.png

Acrobat and Foxit PDF Editor also have equivalent commands, and their online help pages introduce their functions as follows.

• Adobe Acrobat (Apply Layer Overrides) https://helpx.adobe.com/acrobat/using/pdf-layers.html
  Displays all layers, overriding individual settings.

• figure2.png

• Foxit PDF Editor (Apply Layer Overrides) https://www.foxit.com/support/usermanuals.html
  Displays all layers in the document regardless of the settings in the Layer Properties dialog box, and you cannot change layer visibility until you deselect this command or choose Reset To Initial Visibility in the Options menu. However, you are still allowed to rename layers when the command is selected.

• figure3.png

Reading only these help pages, it seems like similar functionality, but the behavior of PDF-XChange Editor and other software seems to be very different.

In the sample file, there are a total of four layers (A to D), all of which are initially set to hidden. Each layer also has a rectangular comment.

• sample.zip

In Acrobat and Foxit PDF Editor, the comments are hidden immediately after the file is opened, but when "Apply Layers Overrides" option is enabled, the rectangular comments that exist on all layers are displayed. The "Apply Layers Overrides" option is marked with a checkmark to confirm that the setting is enabled. If you select the checkbox for each layer, an error dialog box will appear, indicating that the setting cannot be changed. These behaviors seem to be consistent with the description in the online help.

• Acrobat.gif
  
  
  FOXIT.gif

On the other hand, when you select Apply Layers Overrides in the PDF-XChange Editor, no rectangular comments are displayed. Also, there is no checkmark indicating that the Apply Layers Overrides command in the Options menu is enabled, so you cannot tell if the setting is enabled or not. Also, clicking on the checkboxes for each layer allows you to change the visibility of the layer. These behaviors do not seem to match the descriptions in the online help.

• PDFXCE.gif

Similar menu item names do not necessarily mean similar functionality, but I wonder if the behavior in PDF-XChange Editor is what the developers intended.

Thank you for taking the time to read this message.

Best regards,
rakunavi

- PDF-XChange Editor Plus Version: 10.4.0 build 388
- Adobe Acrobat Reader Continuous Release Version 2024.003.20112
- Foxit PDF Editor Pro Version 13.1.2.22442
- OS Version: Windows 11 Home 23H2 Build 22631.3737
- PC Model: Lenovo IdeaPad C340-15IWL, HP All-in-One 22-c0xx

[Daniel - PDF-XChange]

Hello, rakunavi

Thank you for the report, This does seem to be a bit strange in its handling, and certainly does not seem to match the description in the Manuals. I have passed this along for review by the Dev team.

Kind regards,

[rakunavi]

Hello Daniel, thank you for contacting developers.

Thank you for taking time out of your busy schedule.
Please give my best regards to developers.

Best regards,
rakunavi

[Daniel - PDF-XChange]

[rakunavi]

Hello all,

I would like to follow up on my previous report regarding the "Apply Layers Overrides" feature in the Layers pane. I have created a short verification video to demonstrate that this feature currently functions as a "Save Current States as Default" command, which is a significant departure from its intended purpose in the PDF specification and other major PDF editors (Adobe Acrobat/Foxit PDF Editor).

The following outlines the steps shown in the verification. The sample file used is also attached. I hope this video helps clarify why the current implementation is problematic.

1. Open the Layer Properties and check the Default State for each layer. By default, the Default State for Layers A and C is set to On, so Layers A and C will be visible immediately after opening the file.
2. Select all layers, then execute "Toggle Selected Layers" from the Options menu and check the Default State for each layer. While the On/Off status of each layer will be reversed, the Default State for each layer will remain unchanged.
3. Select "Apply Layers Overrides" from the Options menu and check the Default State for each layer. Verify that the current On/Off status of the layers is overwritten as the Default State for each layer.
4. If you save the file, close it, and then reopen it to check the Default State of each layer, you will find that it has been replaced with the settings from when you executed "Apply Layers Overrides" in Step 3. In other words, the Default State of each layer from Step 1 has been discarded, and what was supposed to be a "temporary override" has been fixed as the "initial state."

• figure.png
  
  
  Animation.gif

• sample.pdf

Key Issues Observed:

1. Destructive Behavior:
   As shown in the video, clicking this option permanently overwrites the Default State of the layers within the PDF file. A feature named "Override" should be a non-destructive, session-only toggle (like in Adobe Acrobat), not a permanent modification of the document's initial view settings.
2. Icon Misalignment:
   The current icon features a floppy disk (Save) symbol. This proves that the implementation was intended to "save" changes, which contradicts the very definition of a layer "Override."
   • command.png
3. Manual Contradiction:
   The online manual states: "This option includes layers not listed in the Layers pane." This implies a visibility toggle. However, the actual behavior is an irreversible update to the file's internal configuration.

The Risk:
Users often use "Apply Layers Overrides" simply to inspect hidden content. Because the command name, manual descriptions, and menu layout in PDF‑XChange Editor are very similar to those in Adobe Acrobat and Foxit PDF Editor, users are likely to expect similar behavior from the application. If they unknowingly save the file afterward, the original intended appearance of the document is lost forever. This is a serious UI/UX flaw that can lead to unintentional data alteration in professional environments.

Request:
Could the development team please consider:

• Changing this to a toggle-able (check-marked) state that does not modify the file's Default State.
• If the "Save as Default" functionality is desired, it should be a separate, clearly labeled command (e.g., "Set Current States as Default") to prevent accidental document modification.

Hoping that the above information will be of some help to you.
Thank you for your hard work on this great software.

Best regards,
rakunavi

- PDF-XChange Editor PRO Version: 10.8.4 build 409
- Adobe Acrobat Reader Continuous Release Version 2026.001.21367
- Foxit PDF Editor Pro 13.1.2.22442
- OS Version: Windows 11 Pro / Home 25H2 Build 26200.8037
- PC Model: GMKtec Nucbox M7 Pro with HUION Kamvas Pro 19 / Lenovo IdeaPad C340-15IWL

[Daniel - PDF-XChange]

Hello, rakunavi

Thank you for the report and extensive breakdown of the thought process and comparisons behind this. I agree, this function feels mislabeled at best, or functioning incorrectly at worst.
I have raised the situation with the Dev team for review and consideration, and will be back here as soon as I have heard their thoughts on it.

Kind regards,

[Daniel - PDF-XChange]

Hello, once again!

I have heard back from the Dev team. In the end, it seems the manuals do need an update to accurately reflect the intent here, but here is what they had to say:

There is indeed a mismatch between the command behavior and its help documentation, however our current implementation appears correct and aligned with the intended logic.

The PDF specification does not define any “commands” or how they should behave; it only defines the concept of optional content groups (layers), their properties, and processing rules.
In the ISO 32000-2:2020 (PDF 2.0) Second edition: 2020-12, which as of 2026 is the latest and current version of the PDF specification, specifically in section 8.11.4.5 "Determining the state of optional content groups", it is stated:

• The user may manipulate optional content group states manually or by triggering set-OCG-state actions (see 12.6.4.13, "Set-OCG-state actions") by, for example, clicking links or document outline items. Manual changes shall override the states that were set automatically. The states of these groups remain overridden and shall not be readjusted based on usage application dictionaries with event type View as long as the document is open (or until the user reverts the document to its original state).

This means that layer visibility is initially determined by its properties (Default State, Visibility, Zoom, etc.) when the document is opened. After that, any user interaction creates an override state, which has higher priority but exists only within the current session and is not preserved after reopening the document.
This explains the purpose of the two commands. "Reset to Initial Visibility" clears all user-defined overrides and restores the initial state without modifying the document. "Apply Layers Overrides" takes the current override state and writes it into the layer properties as the new default, effectively modifying the document so that this state is used in future sessions.

Therefore, the name "Apply Layers Overrides" is appropriate because it accurately reflects the action being performed — not just changing visibility temporarily, but explicitly applying and persisting user-defined override states as the new default layer configuration in the document.

I hope this helps to explain that the "apply override" function is working as designed, and intended on our end. Some further discussion has followed, and we will be further investigating how the competition handles these functions to judge what else we could implement as supplementary functions (if necessary).

Kind regards,

[rakunavi]

Hello Daniel, thank you for your detailed response.

I have compared the text of ISO 32000-1:2008 and ISO 32000-2:2020, and as you pointed out, the wording in Section 8.11.4.5 has remained essentially identical. This confirms that the definition of "manual changes" as a transient "override" state (which should not be readjusted as long as the document is open) has been a consistent part of the PDF specification for over 15 years.

• Document management - Portable document format — Part 1: PDF 1.7 (PDF 32000-1:2008), Section 8.11.4.5 "Determining the State of Optional Content Groups"
  The user may manipulate optional content group states manually or by triggering SetOCGState actions (see 12.6.4.12, "Set-OCG-State Actions") by, for example, clicking links or bookmarks. Manual changes shall override the states that were set automatically. The states of these groups remain overridden and shall not be readjusted based on usage application dictionaries with event type View as long as the document is open (or until the user reverts the document to its original state).
• ISO 32000-2:2020 Second edition: 2020-12, Section 8.11.4.5 "Determining the state of optional content groups"
  The user may manipulate optional content group states manually or by triggering set-OCG-state actions (see 12.6.4.13, "Set-OCG-state actions") by, for example, clicking links or document outline items. Manual changes shall override the states that were set automatically. The states of these groups remain overridden and shall not be readjusted based on usage application dictionaries with event type View as long as the document is open (or until the user reverts the document to its original state).

This leads back to my primary concern: the interoperability and risk of data alteration.

Under the same specification, other major editors (Acrobat and Foxit) have long implemented the "Apply Layers Overrides" command as a non-destructive viewing mode to enforce "Usage Application" constraints.

By contrast, PDF-XChange Editor uses this name for a destructive operation that commits these transient states into the permanent D dictionary (Default Configuration). While I understand your logic that you are "applying" the transient state to the file, this interpretation creates a significant "false friend" for professional users.

If the command's purpose is to persist the current visibility to the file structure, it should be named something like "Commit Current Visibility to Default" or "Save Current Layer States". Using the exact same terminology as Acrobat for a fundamentally different (and file-modifying) action poses a serious UI/UX risk where users may unintentionally alter their documents.

I appreciate that the help documentation will be corrected, but I strongly suggest reconsidering the command name or its behavior to align with the industry-standard expectations of "Layer Overrides."

Best regards,
rakunavi

[Sean - PDF-XChange]

Hi Rakunavi,

Thanks for the detailed and informative input here. You are absolutely right, and we are working on addressing this. I will update the manuals shortly, and the development team are considering how to address this and improve it for clarity moving forwards.

Kind regards,

[rakunavi]

Thank you for the response, Sean.

While I appreciate the acknowledgement, I must emphasize that this is more than a documentation error. It is a fundamental functional discrepancy that has existed since this feature was first added to PDF-XChange Editor.

To provide clear evidence, I have attached videos showing the "Apply Layer(s) Overrides" behavior in Acrobat Reader 6.0 (released in 2003) and early builds of PDF-XChange Editor.

As you can see in the evidence:

1. Industry Standard (Acrobat 6.0): Since its introduction 20 years ago, this command has functioned as a non-destructive viewing mode to enforce "Usage Application" constraints.
   
   
   • Animation1.gif
2. PDF-XChange Implementation: When this feature was added to Editor around 2014 (Build 307/308), it adopted a virtually identical command name, UI position, and manual description as Acrobat, but implemented a fundamentally different, destructive logic that overwrites the document's Default Configuration (D dictionary).
   
   
   • Animation2.gif

It is logically inconsistent to claim that this implementation is based on a "unique interpretation of the ISO standard" when every visual element was clearly modeled after the Adobe original. Relying on the ISO text to justify a destructive behavior—where users for 20 years have expected a non-destructive one—poses a serious risk to document integrity.

• figure.png

For a developer to state they will "further investigate the competition" (as Daniel mentioned) 10 years after copying the feature name and description suggests a significant oversight in technical due diligence.

I look forward to seeing a concrete plan to rename this command (e.g., "Commit Current Visibility to Default") or change its behavior to align with the industry-standard logic. Updating the manual alone does not solve the risk of unintentional data loss.

Best regards,
rakunavi

- PDF-XChange Editor Version: 5.5 build 308.2
- Adobe Reader Version: 6.0.1
- OS Version: Windows 11 Pro / Home 25H2 Build 26200.8037
- PC Model: GMKtec Nucbox M7 Pro with HUION Kamvas Pro 19 / Lenovo IdeaPad C340-15IWL

[Sean - PDF-XChange]

Hi Rakunavi,

Thanks for your detailed response - as indicated, you are absolutely correct, and the team are intending on changing the name of this feature for clarity. The team agree that this issue is clearly a lot more than a mere documentation error, and it will be rectified asap.

Thanks for your concern, and kind regards,

[rakunavi]

Hello Sean, thank you for contacting developers.

I am very glad to hear that the team has recognized the significance of this issue and decided to rename the feature.

As a final suggestion to ensure a smooth transition, you might consider changing the corresponding Command IDs at the same time:

• sID / CtrlID: cmd.layersView.applyOverrides
• sID / CtrlID: cmd.layersView.applyOverrides.tip

Since the current English command names and manual descriptions were originally modeled after Acrobat, it is highly likely that volunteer translators for other languages also referenced Acrobat’s official localized manuals for their translations.

If you change only the UI text but keep the old Command IDs, there is a risk that the mismatched or outdated translations will persist in other languages for some time, as translators might not notice the change.

By assigning new IDs alongside the new names, you can trigger a "needs translation" status for localized versions, effectively minimizing confusion across different languages. Furthermore, keeping the old IDs "on ice" would allow you to reuse those existing translations if you ever decide to implement an Adobe-style non-destructive feature in the future.

I apologize if this is overstepping, but as someone who cares deeply about the integrity of this software, I wanted to share this concern to ensure the best possible outcome.

Thank you again for your hard work and for listening to my feedback. Please pass my best regards to the development team.

Best regards,
rakunavi

[Sean - PDF-XChange]

Hi Rakunavi,

Thanks again, I have let the team know.

Kind regards,