# ManYue dense-panel order: test candidate routes with wording and action
Language: en
Canonical: [ManYue dense-panel order: test candidate routes with wording and action]()
中文：[中文 HTML]()
English: [English HTML]()
Published: 2026-11-06T00:00:00+08:00
Modified: 2026-11-06T12:13:22+08:00
Author: Bison
Number candidate routes through a complex page and test dialogue, gutters and action states, separating the first reading from later evidence without treating page-turn gestures as panel navigation.
English translation of the [Chinese original](), translated on 2026-11-06. Original publication dates, attribution, code and version notes are retained.
On a page of differently sized panels, the first visual landing point need not establish the best-supported sequence. Build two candidate routes through one completed dense page in ManYue and test wording and action. This differs from merely addressing panels and assumes no automatic segmentation, panel playback or determination of a uniquely correct order.
## Fix the source page and language direction
Choose an authorised previously read page with intact gutters and readable dialogue, recording work, edition, chapter, page identity and language. Establish the work’s usual page direction rather than deriving panel order from your tap-to-turn settings. Inspect the complete page before detail, retaining its partner for a spread. Begin with five to eight panels rather than a chapter of complex layouts. Resolve missing, mirrored or cropped source material first. Use one complete original arrangement, not an online rearrangement attributed to the creator.
## Assign location labels before ordering
Label locations first, for example upper-left A, upper-right B and lower C, explicitly as locators. Mark uncertain borders around insets or unframed images rather than forcing a rectangular grid onto continuous art. For a crossing balloon, record tail and textual ownership without counting it as another panel. Count the full inventory before routes to catch omissions or repeats. The largest panel is a compositional cue, not an independent rule establishing the start.
## Preserve the actual first reading
Write the route you actually followed and where you paused, lost a referent or expected a missing line. Do not rewrite it as smooth after learning later content. For a long-familiar passage, call this the first route in this rereading, not an original first encounter. Confusion does not prove a layout error; you may have missed wording or used an unfamiliar direction. Record the experience before suggesting changes, giving the recheck a concrete object instead of only a difficult-to-read label.
## Test adjacency through dialogue and connectors
Check question/answer pairs, because/therefore, but and its preceding claim, and here against the depicted location. Balloon position is a clue; speaker attribution also needs tails, action and context. In an invented case, A asks where the key is, C answers on the table, and B takes it. A–C–B may make more sense than A–B–C, subject to time-jump checks. Log support and difficulties for each adjacency rather than declaring an order solely from fluent sentences; suspense or another strand may be intentional.
## Test another route against action states
List a second route with specific support and compare whether cups are full or empty, whether doors are open or closed, character positions and who holds each object. Change order only, not edition or cropping. Note any extra assumption, such as a closed door reopening without explanation. A route needing fewer assumptions may be better supported without being unique. Panels may show one instant from several views, not one added second per move. Keep action and wording evidence separately; preserve conflicts and consult neighbouring pages rather than deleting inconvenient panels.
## Inspect gutters and cross-panel lines
Inspect continuous gutters, shared outer frames, arrows or backgrounds that group panels. A diagonal may indicate motion or decoration rather than order. For insets, check viewpoint and state instead of imposing top-to-bottom position alone. One comparable previously read page from the same work can help, but another work’s convention does not automatically apply. Record how composition supports the route without inventing navigation information or searching for an assumed panel-jump button.
## Leave and return to reread each candidate
Save a supported whole-page bookmark and an external log of labels, both routes and the decisive connection. Leave the reader, return, inspect the whole page and read each route once for omissions, repeats and referent problems. Add stable objects for tall images rather than percentage alone. Attach chapter and full-page identity to favourites instead of replacing the layout with an album of crops. Recheck labels after edition changes: personal labels are not automatically tracked or mapped to new pagination.
## Finish an evidence-based order without forcing uniqueness
Finish with panel inventory, first and alternative routes, wording/action support and unresolved issues. Fluency may rely on later knowledge, and area alone does not establish adjacency. If two readings work, explain how they alter information timing instead of forcing one correct answer. Retain a practical supported route and return references. A complex page can be read slowly without rearranging the file or changing page-turn direction to impose your habits on the work.
## Related guides and sources
[Referencing a panel in ManYue: create a verifiable address within a page](); [ManYue motion-symbol reading: separate speed lines, arrows and object paths]().
Checked on November 6, 2026: [Apple public version information]() lists ManYue 2.0.4, requiring iOS / iPadOS 15.0 or later. Feature scope follows the [official App Store description]() and the installed version. This article provides reading and checking methods you can perform; it does not claim step-by-step physical-device or private-server testing. Manual records, external tools and actually visible controls are identified separately, and personal analysis or code observations are not presented as verified automatic capabilities.