ManYue per-comic preferences: change one vertical comic without changing others

A page-based volume and a vertical comic can need different layouts. Give one entry its own preferences, then check a second book to establish the scope. Entry identity matters: similarly named local and server copies need not share the same preference record.

Choose two books with different needs

Choose a readable page-based reference and an authorised vertical-comic sample. Note each mode, source, chapter and recognisable scene. Use stable content so loading failures do not resemble ignored settings. Re-enter the same identities during testing, especially if one is local and the other is server-based.

Open settings from the target comic

Open the vertical comic’s reader settings and look for the book-specific option. General settings may not have the current entry context needed to show it. Confirm title, source and initial switch state. If the option is absent, retain the general configuration and stop this isolation test rather than assuming another platform’s interface applies.

Change one unmistakable parameter first

Enable the preference and change only the mode to continuous vertical reading. Return to the scene and verify actual movement before adding margins or gestures individually. Leave splitting, processing and automation unchanged initially. A layout preference changes presentation; it does not repair missing source content.

Check the reference book remains unchanged

Leave the vertical comic and reopen the reference. Compare its original direction and layout. If both changed, inspect whether the modification was actually made in the general scope. Revisit the vertical comic too: an enabled switch alone is weaker evidence than both books retaining their intended behaviour.

Distinguish disabling from clearing

Temporarily disabling a preference is different from assuming its stored values were deleted. Inspect what returns when re-enabling it. If a separate clear-book-preferences control exists, record useful values before using it. Its intended scope concerns reading preferences, not comic files, bookmarks or the entire application state.

Check reopening separately from a source change

End the session and reopen the same entry to check persistence. Treat a same-title entry from another service or a new import as a separate identity and inspect its initial behaviour. Do not change sync providers during this test. Establish local entry scope first, before investigating cross-device transfer or file replacement.

Keep the override small

Override only what genuinely differs from the default. Excessive copied values can obscure why one book still behaves differently after general habits change. Keep a short reason and check date, then inspect both a tall image and ordinary dialogue. A comprehensible default and a few justified exceptions are easier to maintain.

Acceptance and troubleshooting

Finish when both books retain their intended layouts after reopening and you understand disable versus clear. For unexpected behaviour, inspect identity, scope and mode conditions before considering version differences. Do not infer that every general option supports per-book storage. Use justified exceptions instead of enabling overrides throughout the collection.

Related guides and sources

ManYue reader controls: page taps and zoom gestures; Read vertical comics in ManYue: continuous scrolling and page joins.

Checked on October 27, 2026: ManYue public version 2.0.3 requires iOS / iPadOS 15.0 or later. Based on the official App Store description and Apple public version lookup. Reader options depend on the installed version and current context. This article describes a checking workflow without claiming step-by-step physical-device or private-server testing, or treating development features as released capabilities.