QUrl::fromUserInput().isRelative() returns false for things like "sound.ogg"
because it converts it to http://sound.ogg
So we use the variant where we give it the document folder, this way if
the file exists returns the local file.
For full urls we get the full url with this second variant so all should
be good
- Ignore autotests sources
- Teach cppcheck about a okular specific define
- Keep the default options from the KDE setup
This at least for me brings the cppcheck entries from "unusable" to "something that probably should be looked into"
Some of the tests relies on having them there, for example verifying
that certain icons is not null or clicking on a widget that has some
size based upon the icons inside them.
Adobe Reader doesn't do it, and with reason, because otherwise we end up
with:
* Run focus in script
* script shows alert()
* form loses focus and gains it again once the alert() is closed
* infinite loop
The same fix we did in e457ceb731 but for
the rest of the widgets
BUGS: 472756
Move XpsHandler bits into XpsPage to parse xml using new classes.
Use QXmlStreamReader instead of QXmlInputSource.
Use QXmlStreamAttributes instead of deprecated QXmlAttributes.
Convert QStringRef return values to string as needed.
In certain usecases, especially for non-linux desktop builds, the
advantage of of dbus is often limited. Provide a way to disable
building with dbus.
Note that this also disables the related functionalities of having a
second okular launch open the document in the first okular.
This also disables the unit tests that tests those features.
Fixes "implicit declaration of function" error with devtoolset-10
(gcc (GCC) 10.2.1 20210130 (Red Hat 10.2.1-11)) in centos7 Docker image
used for building an AppImage.
See also the original source code:
https://github.com/jlaurens/synctex/blob/2020/synctex_parser.c#L104
This adds a test document with most formatting options directly accessible through acrobat.
Currently only the number format functions are tested as they are the only ones implemented.
Original patch is from Oliver Sander, rebased and fixed up by Nicolas Fella
When starting a pinch the user first touches with one finger. That causes the QScroller to enter the pressed state.
Then when the second finger touches and moves this causes the QScroller to interpret it as a scroll. This causes
the view position of the document to move
To avoid this send InputRelease to the scroller when a pinch starts to make sure it is no longer in pressed state.
Also don't send any input to the scroller while the pinch is ongoing to avoid it entering the pressed state again.
BUG: 421755