Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
Fixes https://github.com/mate-desktop/atril/issues/341
|
|
When annotating or filling a form in a document, this must be saved
as a different document as atril does not overwrite documents.
The user can expect to store the modified file in the same place
than the original document, except when the document lives in
a temporary directory (e.g. downloaded automatically with a web
browser), in whose case it must fallback to the Documents
directory (if set) or the the home directory.
Previously, atril assumed the latest directory used, or the place
where an image or attachment was stored last. Such behaviour is
confusing because the latest place opened might have no relation
with the document modified.
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=767611
Adapted from https://gitlab.gnome.org/GNOME/evince/commit/319a6d49
|
|
Use g_debug instead of g_printerr for debug warnings that happen
during normal operation. This way messages are suppressed, unless
the G_MESSAGES_DEBUG variable is set, and we avoid filling everyone's
journal with repetitive debugging info.
https://bugzilla.gnome.org/show_bug.cgi?id=723972
origin commit:
https://gitlab.gnome.org/GNOME/evince/commit/707725e
fixes https://github.com/mate-desktop/atril/issues/315
|
|
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
|
|
|
|
|
|
|
|
|
|
fixes https://github.com/mate-desktop/atril/commit/e6322d0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
follow-up to be5fadcdce164bf7b4cde5487dd0c8837a7efb9d
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
this also disables it when no document is loaded
|
|
follow-up to 9c08159f6ce959f1aa0fc87da265854e9672365e - this action
should be disabled when e.g. a truncated pdf is loaded
|
|
....instead of our own implementation
origin commit:
https://git.gnome.org/browse/evince/commit/?h=gnome-3-0&id=91a30f4
|
|
The code to overlay an icon is unused since commit
https://git.gnome.org/browse/evince/commit/?id=808285c
origin commit:
https://git.gnome.org/browse/evince/commit/?id=171918f
|
|
origin commit:
https://git.gnome.org/browse/evince/commit/?h=gnome-3-8&id=38528f9
|
|
.... and misc_paint_one_page()
origin commit:
https://git.gnome.org/browse/evince/commit/?h=gnome-3-8&id=a610d49
|
|
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
|
|
origin commit:
https://git.gnome.org/browse/evince/commit/?h=gnome-3-8&id=3fd4162
|
|
taken from:
https://github.com/GNOME/evince/commit/91ac78bc587eb2ac931136c9da9609b142410209
|
|
Fixes https://github.com/mate-desktop/atril/issues/308
|
|
|
|
|
|
otherwise atril crashes
https://bugzilla.gnome.org/show_bug.cgi?id=685591
origin commit:
https://git.gnome.org/browse/evince/commit/?h=gnome-3-8&id=b4bf316
|
|
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
|
|
|