Skip to content

fix: fix dynamic zoom display scaling issues in writer#15550

Open
printfdebugging wants to merge 1 commit intomainfrom
private/printfdebugging/dynamic-zoom-scaling-issues-fix
Open

fix: fix dynamic zoom display scaling issues in writer#15550
printfdebugging wants to merge 1 commit intomainfrom
private/printfdebugging/dynamic-zoom-scaling-issues-fix

Conversation

@printfdebugging
Copy link
Copy Markdown
Contributor

  • calculateAvailableSpace gets scaled up values for document and container width, so no need to scale that further.

  • panBy doesn't use scaled up values, but getDocumentScrollOffset returns the offset with scaling applied. So we need to divide that by the scaling factor.

Change-Id: I039761ae5c986c4a9959be509eb46a39370c252c

  • Resolves: #
  • Target version: main

Summary

TODO

  • ...

Checklist

  • I have run make prettier-write and formatted the code.
  • All commits have Change-Id
  • I have run tests with make check
  • I have issued make run and manually verified that everything looks okay
  • Documentation (manuals or wiki) has been updated or is not required

- calculateAvailableSpace gets scaled up values for document and
  container width, so no need to scale that further.

- panBy doesn't use scaled up values, but getDocumentScrollOffset
  returns the offset with scaling applied. So we need to divide that by
  the scaling factor.

Signed-off-by: Sahil Gautam <sahil.gautam@collabora.com>
Change-Id: I039761ae5c986c4a9959be509eb46a39370c252c
@printfdebugging
Copy link
Copy Markdown
Contributor Author

please don't merge this yet. although this improves things, it assumes that the document and canvas size are always in sync with the scaling. but as it turns out on browser zoom changes, app.dpiScale changes, but the document and canvas dimensions barely change with that. so i need to investigate a bit more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: To Review

Development

Successfully merging this pull request may close these issues.

1 participant