| Summary: | Unable to save large scans. | ||
|---|---|---|---|
| Product: | [Applications] Skanpage | Reporter: | Roke Julian Lockhart Beedell <4wy78uwh> |
| Component: | general | Assignee: | Alexander Stippich <a.stippich> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 24.02.2 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/utilities/skanpage/-/commit/fcf0af8c9a041f551e018da7ba98188935884f21 | Version Fixed/Implemented In: | |
| Sentry Crash Report: | |||
| Attachments: |
"Export all" to (OCR) PDF.
Output PDF. "Save all" and "Save as" (to TIFF and PDF). |
||
|
Description
Roke Julian Lockhart Beedell
2024-05-28 14:19:36 UTC
Created attachment 169915 [details]
Output PDF.
Created attachment 169916 [details]
"Save all" and "Save as" (to TIFF and PDF).
Git commit fcf0af8c9a041f551e018da7ba98188935884f21 by Alexander Stippich. Committed on 23/06/2024 at 18:06. Pushed by astippich into branch 'master'. raise QImageReader allocation limit back to Qt5 values Related: bug 486984 M +3 -0 src/Skanpage.cpp https://invent.kde.org/utilities/skanpage/-/commit/fcf0af8c9a041f551e018da7ba98188935884f21 (In reply to Alexander Stippich from comment #3) Does the fact that a maximum allocated value exists mean that it would be possible to hit it at an even higher DPI, or is it so absurdly high that I don't need to worry? Thanks for the work. Theoretically possible, but the current limit mirrors Qt5's behavior. There were zero issues with that. |