Skip to content

fix(reader): correct the wide image logic again#640

Merged
everpcpc merged 1 commit intoeverpcpc:mainfrom
dyphire:reader
Mar 10, 2026
Merged

fix(reader): correct the wide image logic again#640
everpcpc merged 1 commit intoeverpcpc:mainfrom
dyphire:reader

Conversation

@dyphire
Copy link
Copy Markdown
Contributor

@dyphire dyphire commented Mar 10, 2026

The limitation of hiding the split wide page option in double page mode is no longer necessary, it already works in this mode.

@dyphire dyphire changed the title fix(reader): correct the wide image processing logic again fix(reader): correct the wide image logic again Mar 10, 2026
@dyphire dyphire force-pushed the reader branch 2 times, most recently from f1250fd to 0bdfad9 Compare March 10, 2026 02:51
@everpcpc
Copy link
Copy Markdown
Owner

Thanks but there are more changes needed. Please check #641 if it match your needs.

@dyphire
Copy link
Copy Markdown
Contributor Author

dyphire commented Mar 10, 2026

Thanks but there are more changes needed. Please check #641 if it match your needs.

#641 was very inappropriate and I commented there.

@everpcpc
Copy link
Copy Markdown
Owner

@codex review

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e9e4cc8237

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

allowDualPairs: isActuallyUsingDualPageMode,
forceDualPairs: forceDualPagePairs,
splitWidePages: effectiveSplitWidePages,
pageCurl: AppConfig.pageTransitionStyle == .pageCurl,
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Recompute view items when transition style changes

regenerateViewState() now makes viewItems depend on AppConfig.pageTransitionStyle == .pageCurl, but there is no corresponding update path when users change “Page Transition Style” in the reader settings (DivinaReaderView only calls updateDualPageSettings, updatePageLayout, and updateSplitWidePageMode on change). As a result, switching between non-curl and page-curl mid-session can leave wide-page items in the old layout until some unrelated regeneration happens, so the displayed split behavior no longer matches the active transition style.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fix

@dyphire dyphire force-pushed the reader branch 3 times, most recently from 47b4616 to b29b1bc Compare March 10, 2026 03:54
@dyphire
Copy link
Copy Markdown
Contributor Author

dyphire commented Mar 10, 2026

I'm kind of confused about this compiler error.

@everpcpc
Copy link
Copy Markdown
Owner

regenerateViewState is a private func

@dyphire
Copy link
Copy Markdown
Contributor Author

dyphire commented Mar 10, 2026

regenerateViewState is a private func

Ah, stupid mistake. Fix.

@everpcpc everpcpc merged commit 73a7112 into everpcpc:main Mar 10, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants