Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
A recent update to libwebkitgtk2gtk-4.1 breaks using WebKitWebView
in a GtkOffscreenWindow.
Disable the thumbnail sidebar with epub documents, and disable
updating the GtkWindow thumbnail.
ref:
https://github.com/WebKit/WebKit/commit/8d7385fad3ffb31d0c438e6b6a50dffb4390840c
Fixes: #631.
|
|
Signed-off-by: Oz Tiram <[email protected]>
|
|
Signed-off-by: Oz Tiram <[email protected]>
|
|
Mostly copy and paste from linuxmint/xreader
Signed-off-by: Oz Tiram <[email protected]>
|
|
Signed-off-by: Oz Tiram <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Not everyone who reads PDF's is necessarily a LaTeX user.
These changes allow users to install atril without the huge bagage
of tex-live on systems where synctex isn't provided as a stand alone
library.
|
|
The memory leak was caused by a g_signal_connect
which was never disconnected. This patch makes
sure the signal is disconnected and the job is
cancelled before creating another rendering job.
It additionally introduces a helper function to
cleanly finalize the job.
origin commit:
https://gitlab.gnome.org/GNOME/evince/commit/939c434
|
|
This reverts commit 00fad2c0d0fcdade570a08f046e85a4558f1fc0c.
and fixes https://github.com/mate-desktop/atril/issues/404
|
|
|
|
If view->pressed_button is left set, when the Drag and Drop operation completes, Atril will act as if it is still in a selection event.
Adapted from: https://gitlab.gnome.org/GNOME/evince/commit/92828bb797742e04aadbfdd62ba1da36837c37cf
|
|
|
|
to determine window size.
Replace {Width/Hight}OfScreen which works only with X11
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Replace deprecated --header --body options
inspired by:
https://gitlab.gnome.org/GNOME/evince/commit/f6952c2
|
|
|
|
such that hi-dpi conditionals aren't needed.
origin commit:
https://github.com/linuxmint/xreader/commit/df3cdc6
|
|
Make sure not to move the caret in the wrong direction when restoring
the visual line X offset, in case the visual and logical order is
slightly different.
The algorithm used to move the cursor on the next line and restore the
X position across lines works as follows:
1. Move `cursor_offset` to the next line by incrementing it until
reaching a line break;
2. Find the Y coordinate corresponding to the new cursor_offset;
3. Find the text closest to the new Y coordinate and the previous X
coordinate.
4. Move cursor_offset to the text at this new (X, Y) location.
The issue lies in step 3, which can find a position on a different line
than expected in case several lines have a nearly the same Y position.
Evince references:
* https://gitlab.gnome.org/GNOME/evince/issues/889
* https://gitlab.gnome.org/GNOME/evince/merge_requests/81
* https://gitlab.gnome.org/GNOME/evince/commit/dddd98b4c7922e2906bba6a31afa07837ae6c39c
|
|
|
|
|
|
origin commit:
https://git.gnome.org/browse/evince/commit/?h=gnome-3-8&id=38528f9
|
|
So it can be styled with CSS.
https://bugzilla.gnome.org/show_bug.cgi?id=653294
origin commit:
https://git.gnome.org/browse/evince/commit/?h=gnome-3-8&id=7a6b53a
https://git.gnome.org/browse/evince/commit/?h=gnome-3-8&id=4657961
|
|
This modifies ev_page_accessible_get_range_for_boundary to ensure that
the start and end offsets it returns are within the allowed range.
https://bugzilla.gnome.org/show_bug.cgi?id=777992
origin commit:
https://git.gnome.org/browse/evince/commit/?id=e95a4e3
|
|
ev_page_accessible_get_substring gets called with out of bounds values
leading to a crash. Clamp start_offset to a valid range.
https://bugzilla.gnome.org/show_bug.cgi?id=777992
origin commit:
https://git.gnome.org/browse/evince/commit/?id=b34f357
|
|
inspired by:
https://git.gnome.org/browse/evince/commit/?h=gnome-3-8&id=a56186e
|
|
taken from:
https://github.com/GNOME/evince/commit/91ac78bc587eb2ac931136c9da9609b142410209
|
|
Fixes https://github.com/mate-desktop/atril/issues/308
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=693749
origin commit:
https://git.gnome.org/browse/evince/commit/?h=gnome-3-8&id=53d6a3
|
|
It wasn't correctly set as modal.
origin commit:
https://git.gnome.org/browse/evince/commit/?h=gnome-3-2&id=987aab6
|
|
....in ev-view-presentation
This was introduced again in previous commit.
|
|
Create rendering jobs with a scale that incorporate the scale factor of
the widget, and then use cairo_surface_set_device_scale() to make the
resulting surfaces render at the correct size. Handle changes to the scale
factor both for the cached surfaces, and also for the monitor dimensions,
which are reported in scaled coordinates.
https://bugzilla.gnome.org/show_bug.cgi?id=723431
origin commit:
https://git.gnome.org/browse/evince/commit/?id=37c13b
|
|
Fail when device scale is not 1 if hidpi is not available, we were doing
the opposite.
origin commit:
https://git.gnome.org/browse/evince/commit/?id=90a258
|
|
Make EvPixbufCache generate surfaces with extra resolution based on
gtk_widget_get_scale_factor(). Handle cairo surfaces with a device
scale in ev_view_draw(). Trigger an update of the pixbuf cache when
the scale factor changes.
https://bugzilla.gnome.org/show_bug.cgi?id=723431
origin commit:
https://git.gnome.org/browse/evince/commit/?id=a612f8
|