- 07 Jul, 2013 5 commits
-
-
Otherwise, when opening a document at page 1, and no jumps are added, bisect does not understand it has to initialize the bisect range, and does not move from page 1. Signed-off-by:
Sebastian Ramacher <sebastian+dev@ramacher.at>
-
Moritz Lipp authored
-
After page_set cb_view_hadjustment_changed must be called so that when zoom-center is enabled, the page is recentered. Signed-off-by:
Sebastian Ramacher <sebastian+dev@ramacher.at>
-
Signed-off-by:
Sebastian Ramacher <sebastian+dev@ramacher.at>
-
Sebastian Ramacher authored
Move some bisect state to zathura_t and manipulate the jumplist that much. Signed-off-by:
Sebastian Ramacher <sebastian+dev@ramacher.at>
-
- 29 Jun, 2013 1 commit
-
-
This makes jumping works accurately, even if the document is scaled up or down. Signed-off-by:
Sebastian Ramacher <sebastian+dev@ramacher.at>
-
- 20 Jun, 2013 3 commits
-
-
Sebastian Ramacher authored
Signed-off-by:
Sebastian Ramacher <sebastian+dev@ramacher.at>
-
Signed-off-by:
Sebastian Ramacher <sebastian+dev@ramacher.at>
-
- Allow the user to always start with the very last (or first) jump on the jumplist when pressing ^o (or ^i), while the jumplist iterator is pointing to the last (or first) jump, and the document is not currently at the position of this pointed-to jump. This is instead of jumping directly to the previous/next jump, and skipping the last/first one. - Don't jump to the current jump pointed to by the jumplist iterator, if there is no more next jumps, and the jump direction is FORWARD. - Don't jump to the current jump pointed to by the jumplist iterator, if there is no more previous jumps, and the jump direction is BACKWARD. Signed-off-by:
Sebastian Ramacher <sebastian+dev@ramacher.at>
-
- 10 Jun, 2013 2 commits
-
-
- Don't delete the elements on the right of the current one, when appending a new jump to the jumplist, because this makes no sense at all; the point of the jumplist in the first place is to remember previously jumped-to positions in the document, so there is no need to delete anythings except to trim the oldest entries from the beginning to maintain the maximum size. This also makes us compatible with the Vim way of doing things. - Make the jumplist mechanism functional on the same page; if we followed a link to a target on the same page, remember the adjustments before and after following the link. The same holds for navigating search results on the same page. - Implement position_set and use it instead of position_set_delayed when following links in order to give zathura_jumplist_save a chance to record the exact adjustments of the link target. Otherwise, it will always record the adjustments after going to the target page, but before going to the exact position within it. - Don't consider movements with ^i and ^o as jumps :) - Don't use page_set followed by setting the adjustments in sc_jumplist, because this is redundant and causes clutter when using ^i and ^o, as the adjustments is set twice this way (once in page_set and again in position_set_delayed). It's enough to only update the page number on the statusbar and then set the adjustments. - Hide implementation details (zathura_jumplist_save and zathura_jumplist_append), and make things more consistent by exporting and using only zathura_jumplist_add for adding new entries. The end result: A more slick jumping experience :-) Signed-off-by:
Sebastian Ramacher <sebastian+dev@ramacher.at>
-
This patch activates the last aborted search when pressing the search shortcuts ('n' or 'N'). To avoid confusion, and to make things more predictable, I've chosen to always reactivate an aborted search starting from the beginning (or end, in case of 'N' or '?') of the current page, as opposed to Vim which continues from the next search term each time the search is reactivated. Searching using '/' or '?' doesn't center the view at the current search term like when using 'n' or 'N', so we fix this here. Also, I managed to work around the issue of the thin rectangular margins that show around the previously-highlighted search terms after the search is aborted (either explicitly or as a result of following links), by redrawing the page widget (only if it's visible) instead of redrawing the rectangles covering the highlighted search terms. Signed-off-by:
Sebastian Ramacher <sebastian+dev@ramacher.at>
-
- 02 Jun, 2013 1 commit
-
-
Signed-off-by:
Sebastian Ramacher <sebastian+dev@ramacher.at>
-
- 08 May, 2013 1 commit
-
-
Moritz Lipp authored
-
- 02 Apr, 2013 3 commits
-
-
Signed-off-by:
Sebastian Ramacher <sebastian+dev@ramacher.at>
-
This uses the jumplist to implement a bisect functionality between the last two jump points. ^j and ^k are bound to bisect forward and backward respectively. Signed-off-by:
Sebastian Ramacher <sebastian+dev@ramacher.at>
-
Call cb_view_hadjustment_changed to set horizontal position in navigation shortcuts: sc_navigate, sc_goto. Signed-off-by:
Sebastian Ramacher <sebastian+dev@ramacher.at>
-
- 29 Mar, 2013 1 commit
-
-
This will not scroll the document when pressing 'f' or 'F', just to make the behavior consistent with activating the inputbar using ':'. Signed-off-by:
Sebastian Ramacher <sebastian+dev@ramacher.at>
-
- 23 Mar, 2013 3 commits
-
-
Add a new adjust mode that is set when focusing the inputbar and disables adjusting the vertical scrollbar. As a result, focusing the inputbar doesn't scroll the document, leading to better results when changing pages from the inputbar (e.g. using bookmarks). Reported-by:
Marwan Tanager <marwan.tngr@gmail.com> Signed-off-by:
Sebastian Ramacher <sebastian+dev@ramacher.at>
-
Instead of guesstimating the values of the scrollbars adjustments after a change in zoom level, connect callbacks to the "changed" GtkAdjustment event (which is emitted when the bounds or page_size of the adjustment change, e.g. when the zoom level changes), and compute the new values from there. The previous adjustment values are tracked in zathura->ui.hadjustment and zathura->ui.vadjustment (and updated by signal handlers as well), so that the view's position can be maintained while zooming. cb_view_hadjustment_changed() centers the page horizontally if a "best-fit" or "width" zoom is being performed, or if "zoom-center" is true; otherwise, it keeps the view horizontally centered around the same area of the page. cb_view_vadjustment_changed() always keeps the view vertically centered around the same area of the page. Many thanks to Marwan Tanager for thoroughly reviewing the various stages of this patch, and actually coming up with a working solution. Signed-off-by:
Sebastian Ramacher <sebastian+dev@ramacher.at>
-
This wasn't correct. Padding is already accounted for: scale = (width - (pages_per_row - 1) * padding) / (pages_per_row * cell_width) If you add padding on the denominator, you end up with black margins on the sides of the window, which isn't what padding is for (i.e. insert a gap between rendered pages), and defeats the purpose of a "best-fit". Signed-off-by:
Sebastian Ramacher <sebastian+dev@ramacher.at>
-
- 17 Mar, 2013 1 commit
-
-
If '--page [number]' (or '-P [number]') is given on the command-line, the document is opened at the specified page number. Negative numbers are allowed, and denote a page number starting from the end of the document. See issue 275 <http://bugs.pwmt.org/issue275 >. Reported-by:
bob <sean258@gmail.com>
-
- 03 Mar, 2013 2 commits
-
-
Sebastian Ramacher authored
Signed-off-by:
Sebastian Ramacher <sebastian+dev@ramacher.at>
-
Signed-off-by:
Sebastian Ramacher <sebastian+dev@ramacher.at>
-
- 07 Feb, 2013 1 commit
-
-
Moritz Lipp authored
Thanks to Marwan Tanager
-
- 19 Dec, 2012 1 commit
-
-
Rob Cornish authored
Signed-off-by:
Sebastian Ramacher <sebastian@ramacher.at>
-
- 13 Dec, 2012 1 commit
-
-
The width of the vertical scrollbar (if there is one) needs to be substracted from the width of the GtkScrolledWindow in order to obtain the correct dimensions of the view area. See issue 27 <http://bugs.pwmt.org/issue27 >. It also deals better with documents where pages don't all have the same size. Reported-by:
Andreas Weinlich <business@weinlich.org> Signed-off-by:
Sebastian Ramacher <sebastian+dev@ramacher.at>
-
- 10 Dec, 2012 1 commit
-
-
Signed-off-by:
Sebastian Ramacher <sebastian+dev@ramacher.at>
-
- 07 Dec, 2012 1 commit
-
-
This is useful when the text of the link doesn't match its target. The default key is set to 'F'. See issue 266 <http://bugs.pwmt.org/issue266 >. Reported-by:
Iron <o380770@rtrtr.com> Signed-off-by:
Sebastian Ramacher <sebastian+dev@ramacher.at>
-
- 06 Dec, 2012 2 commits
-
-
The scroll-wrap option used to only change the behavior of 'J' and 'K' (i.e. moving one page forward/backward). Now, if scroll-wrap is true and the top of the first page is shown, pressing 'k' will show the bottom of the last page; conversely, when at the bottom of the last page, pressing 'j' will show the top of the first page. Signed-off-by:
Sebastian Ramacher <sebastian+dev@ramacher.at>
-
When set to true, it used to _not_ wrap around the begining/end. Now it wraps if set to true, and it doesn't if set to false. Signed-off-by:
Sebastian Ramacher <sebastian+dev@ramacher.at>
-
- 09 Oct, 2012 1 commit
-
-
Moritz Lipp authored
-
- 06 Oct, 2012 1 commit
-
-
Moritz Lipp authored
-
- 05 Oct, 2012 1 commit
-
-
Moritz Lipp authored
-
- 19 Sep, 2012 1 commit
-
-
Moritz Lipp authored
-
- 17 Sep, 2012 4 commits
-
-
Moritz Lipp authored
-
Sebastian Ramacher authored
-
if scroll-page-aware is set, scrolling by full and half pages stops at page boundaries (as djview4 does it on <space> and <backspace>). Signed-off-by:
Sebastian Ramacher <sebastian+dev@ramacher.at>
-
The default of 0.1 keeps 10% of a page visible on a full-page scroll. Signed-off-by:
Sebastian Ramacher <sebastian+dev@ramacher.at>
-
- 03 Sep, 2012 1 commit
-
-
Moritz Lipp authored
-
- 02 Sep, 2012 1 commit
-
-
Sebastian Ramacher authored
Otherwise jump positions are off after changing the zoom level.
-