Skip to content

Deskew vs oblique: split parameter model and copy semantics (follow-up from #113) #117

Description

@pablogventura

Context

Detailed feedback from @zvezdochiot on #113 (see that thread and PR #114) describes limitations beyond the current PR scope:

  • Difficulties copying parameters between pages when deskew and oblique are only partially decoupled.
  • Manual oblique adjustments interacting badly with Auto deskew for batch/copy flows.
  • Need to re-enable Auto oblique after Manual→Auto toggles even when the user had already opted in.

Proposed direction (discussion)

Treat deskew (rotation) and oblique (shear) as separate parameter domains (e.g. ParamsDeskew / ParamsOblique), each with its own Auto/Manual mode and angle value, and separate “Apply to…” / copy logic.

Scope

This issue is for design + implementation planning. It should not block merging PR #114 unless maintainers explicitly want a single mega-PR.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions