Skip to content

1.0.1

Choose a tag to compare

@ShiroiKuma0 ShiroiKuma0 released this 24 Apr 00:16

1.0.1

Release focused on reader polish and dictionary UX.

Reader

  • Vertical-text books no longer show a large empty gap at the bottom of every paragraph column. Root cause was the margin-bottom in the per-book appearance CSS stealing physical column-bottom space in writing-mode: vertical-rl; replaced with the writing-mode-aware margin-block-end logical property so paragraph spacing applies on the correct axis.
  • Primary/Secondary font picks in per-book appearance now actually take effect. Previously they set --font-family-serif / --font-family-sans-serif CSS variables that TTU's own rules ignored; now we emit a forceful .book-content, p, div, span { font-family: ... !important } override that beats TTU's defaults. Labels renamed from "Font family (serif/sans-serif)" to Primary font / Secondary font.
  • New per-book Writing mode setting (Horizontal / Vertical) in the appearance dialog. Primary-language Japanese books default to vertical; everything else defaults to horizontal. Setting is persisted per book.
  • Per-book state now keyed by the TTU SPA's internal book id instead of the widget item, so the correct book's appearance and position load when reopening.
  • Audio toolbar polish: smaller filename overlay, SRT filename shown separately, +N subtitle count indicator in the title.

Dictionary

  • Tapping a word in a book no longer raises the soft keyboard. The recursive dictionary page previously used a FloatingSearchBar whose internal TextField auto-focused on open, raising the IME on every lookup and requiring two back presses to exit. Replaced with a minimal AppBar (title shows the search term, plus a half-screen toggle and a magnifying-glass icon) and a plain results body. Tapping the magnifying glass opens a dedicated search dialog — keyboard rises there because you explicitly asked for it.

Build / Packaging

  • Android versionCode now computed from the full pubspec X.Y.Z+N instead of just N, so codes strictly increase across every release and dev build forever. The old formula regressed at every release (dropping from a dev build's +25 down to the release's 1), causing the OS installer to reject releases as downgrades.