[okular] [Bug 421780] Most ways of navigating a document not working (Qt 5.15)
https://bugs.kde.org/show_bug.cgi?id=421780 --- Comment #7 from Bernhard Rosenkränzer --- Created attachment 130671 --> https://bugs.kde.org/attachment.cgi?id=130671=edit Partial revert that fixes it The attached patch, a partial revert of the problematic commit, "fixes" the issue (but of course destroys the advantages of using QScroller). I'll keep this in our package until the real problem is sorted out, it's not perfect but better than nothing, at least it restores what was working in 19.12.x -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 424810] Assert crash when selecting quick annotation tool that was added in the config dialog
https://bugs.kde.org/show_bug.cgi?id=424810 Albert Astals Cid changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/okular/commit/72f5a2db ||089178c1e9eca82ba5a9a97fff2 ||a49dc Version Fixed In||1.11.0 --- Comment #6 from Albert Astals Cid --- Git commit 72f5a2db089178c1e9eca82ba5a9a97fff2a49dc by Albert Astals Cid, on behalf of Simone Gaiarin. Committed on 05/08/2020 at 22:49. Pushed by aacid into branch 'release/20.08'. Find built-in tool corresponding to quick tool at runtime In this way it is possible to drop the `sourceId` attribute from the quick tools definition. This simplifies the code logic and makes it easier to update user settings from the previous version of Okular (because there is no need to add the attribute `sourceId` This also fixes the crash due to the fact that `sourceId` was not correctly created when a quick annotation is created from the Annotation page of Okualr Settings. FIXED-IN: 1.11.0 M +1-1autotests/CMakeLists.txt M +19 -2autotests/annotationtoolbartest.cpp M +30 -5ui/annotationactionhandler.cpp M +5-0ui/data/tools.xml M +12 -6ui/data/toolsQuick.xml M +17 -3ui/pageviewannotator.cpp https://invent.kde.org/graphics/okular/commit/72f5a2db089178c1e9eca82ba5a9a97fff2a49dc -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 424670] mousewheel scroll at end of document jumps incorrectly
https://bugs.kde.org/show_bug.cgi?id=424670 Albert Astals Cid changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Albert Astals Cid --- .kde/share is junk from kde4 era Yes, i made sure of that. I guess you can try posting those to see if it helps, cleanup the recently open files if you don't want to leak that info. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 424817] Ugly rendering of images containing text in PDF files
https://bugs.kde.org/show_bug.cgi?id=424817 Albert Astals Cid changed: What|Removed |Added Resolution|WAITINGFORINFO |UPSTREAM Status|NEEDSINFO |RESOLVED --- Comment #13 from Albert Astals Cid --- Yeah i meant "resampling images with text" Yeah makes sense, your 100% is about 875 pixels wide while mine is 1315 pixels wide, since my screen is smaller, i need more pixels to make it 23.5 cm than you, so i see a better image. Anyhow, not an Okular bug, poppler is doing the resampling, so it needs a bug there https://gitlab.freedesktop.org/poppler/poppler/-/issues -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 421780] Most ways of navigating a document not working (Qt 5.15)
https://bugs.kde.org/show_bug.cgi?id=421780 --- Comment #6 from Bernhard Rosenkränzer --- The problem seems to be d->scroller->scrollTo(d->scroller->finalPosition() + QPoint(0, 100 * nSteps), 0); in slotScrollDown() in ui/pageview.cpp not having any effect (even though nSteps == 1) when it is called by the keyboard event and wheel event handlers. I've never used QScroller, so I'm not familiar with its internals -- but at a first glance, looks like a Qt bug and makes me wonder why others aren't seeing this (we're using stock qt 5.15). -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 421780] Most ways of navigating a document not working (Qt 5.15)
https://bugs.kde.org/show_bug.cgi?id=421780 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #5 from Albert Astals Cid --- Not a surprise, that patch breaks everything. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 263042] XFA Forms are not supported
https://bugs.kde.org/show_bug.cgi?id=263042 --- Comment #24 from Albert Astals Cid --- Please can you attach such a pdf with XFA forms that works in evince and not in Okular? -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 421780] Most ways of navigating a document not working (Qt 5.15)
https://bugs.kde.org/show_bug.cgi?id=421780 Bernhard Rosenkränzer changed: What|Removed |Added Version|1.10.1 |1.10.80 --- Comment #4 from Bernhard Rosenkränzer --- Finally got around to bisecting this. The culprit is commit 51b90ecd73e37b9646d8a4bbb51e4fa815942912 Author: kezi olio Date: Fri Nov 15 16:08:25 2019 + Add kinetic scrolling & smooth navigation with cursor keys -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 263042] XFA Forms are not supported
https://bugs.kde.org/show_bug.cgi?id=263042 --- Comment #23 from Reissner --- in contrast to okular, evince seems to support xfa. How did they do that if it is so complicated? -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 424817] Ugly rendering of images containing text in PDF files
https://bugs.kde.org/show_bug.cgi?id=424817 --- Comment #12 from Jan Rathmann --- (In reply to Albert Astals Cid from comment #10) > This is probably related to screen sizes. Your screen is much bigger than > mine but with the same resolution, so you get less quality than me "per > percentage". Because for your 100% less pixels are needed that for my 100%, > so i see it better than you at 100%. > > Can you attach a screenshot of the document at 100% in your screen to > confirm? Ok, did that. So if I got this right the bug appears only on lowdpi screens like mine? > Anyhow, [mostly] that solved that, this is a poppler bug in which the Splash > renderer seems to be not so great when resampling text. I'm a bit confused - do you mean "rescaling images" instead of "resampling text"? (since my test document doesn't contain any "real" text but a bitmap image that shows text.) -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 424817] Ugly rendering of images containing text in PDF files
https://bugs.kde.org/show_bug.cgi?id=424817 --- Comment #11 from Jan Rathmann --- Created attachment 130657 --> https://bugs.kde.org/attachment.cgi?id=130657=edit Screenshot rendering of test.pdf with Okular (zoom level 100%) -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 425030] feature request: xfa support
https://bugs.kde.org/show_bug.cgi?id=425030 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 263042 *** -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 263042] XFA Forms are not supported
https://bugs.kde.org/show_bug.cgi?id=263042 Christoph Feck changed: What|Removed |Added CC||rei3...@arcor.de --- Comment #22 from Christoph Feck --- *** Bug 425030 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 425030] New: feature request: xfa support
https://bugs.kde.org/show_bug.cgi?id=425030 Bug ID: 425030 Summary: feature request: xfa support Product: okular Version: unspecified Platform: unspecified OS: All Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: rei3...@arcor.de Target Milestone: --- Created attachment 130655 --> https://bugs.kde.org/attachment.cgi?id=130655=edit some pdf containing xfa forms SUMMARY Currently, documents containing xfa forms are not supported. As these are used by many official documents, xfa support is desirable. STEPS TO REPRODUCE 1. Open a pdf with xfa forms like the one attached 2. 3. OBSERVED RESULT Message: "This document has XFA forms, which are currently unsupported" EXPECTED RESULT support for xfa forms. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
