1. 02 Jun, 2018 3 commits
  2. 01 Jun, 2018 2 commits
  3. 22 May, 2018 1 commit
  4. 11 Mar, 2018 2 commits
  5. 25 Feb, 2018 1 commit
  6. 22 Feb, 2018 1 commit
  7. 15 Feb, 2018 1 commit
  8. 12 Feb, 2018 1 commit
    • Jeremie Knuesel's avatar
      Distinguish zoom and scale, always apply DPI correction on scale · d625c0d9
      Jeremie Knuesel authored
      Replace scale with zoom in most cases. Scale means pixels per point, as
      before. The zoom is the screen-size / document-size ratio: a zoom of 1
      means that the document should have the same size on screen as on paper.
      This fixes many issues with the previous DPI changes, e.g. with link and
      search rectangles.
  9. 28 Jan, 2018 1 commit
  10. 30 Dec, 2017 1 commit
  11. 07 Nov, 2014 1 commit
  12. 27 Oct, 2014 2 commits
  13. 19 Jan, 2014 1 commit
  14. 31 Oct, 2013 2 commits
  15. 30 Oct, 2013 2 commits
  16. 27 Oct, 2013 1 commit
  17. 26 Oct, 2013 2 commits
    • Abdo Roig-Maranges's avatar
      use the new document functions in link evaluation · efc7d23f
      Abdo Roig-Maranges authored
      We now use the data available on the document object to compute the
      exact positioning of the link target.
      This way we get rid of page_calculate_offset, which uses explicit GTK
    • Abdo Roig-Maranges's avatar
      add functions to compute page positions · 030a8c65
      Abdo Roig-Maranges authored
      The plan is to put in adjustment.c every piece of code that has to do
      with document positioning, either computing it from data on the document
      side, or talking to GTK.
      We want to have at our disposal functions to compute sizes and positions
      without having to ask for it to a GTK widget. The new functions are:
       - move page_calc_height_width to adjustment.c
       - add page_calc_position that rotates a position relative to a page
         according to the rotation settings.
       - add position_to_page_number that computes the number of a page
         sitting at a given position (given in document-relative coordinates)
       - add page_number_to_position that computes the position (in document
         relative coordinates) that will be placed at the center of the viewport.
       - add page_is_visible that checks whether the given page intersects the
  18. 25 Oct, 2013 1 commit
  19. 26 Jul, 2013 1 commit
  20. 21 Jun, 2013 1 commit
    • Marwan Tanager's avatar
      Move calls to zathura_jumplist_add surrounding zathura_link_evaluate to... · d9f8750c
      Marwan Tanager authored
      Move calls to zathura_jumplist_add surrounding zathura_link_evaluate to zathura_link_evaluate itself
      This is just in case that zathura_link_evaluate returns without evaluating the
      link, which would result in a new jump being added for the current position,
      but without adding a corresponding jump for the target position (actually a
      second one would be added but the check in zathura_jumplist_add would prevent
      it from being appended on the linked list since it's position would be the same
      as the current one, because the link haven't been evaluated).
      Signed-off-by: Sebastian Ramacher's avatarSebastian Ramacher <sebastian+dev@ramacher.at>
  21. 10 Jun, 2013 1 commit
    • Marwan Tanager's avatar
      Enhancements/Cleanups for the jumplist mechansim · afd008f4
      Marwan Tanager authored
      	- 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's avatarSebastian Ramacher <sebastian+dev@ramacher.at>
  22. 02 Apr, 2013 1 commit
  23. 23 Feb, 2013 1 commit
  24. 07 Dec, 2012 1 commit
  25. 31 Oct, 2012 1 commit
  26. 08 Oct, 2012 1 commit
  27. 09 Sep, 2012 1 commit
  28. 06 Jun, 2012 2 commits
  29. 28 May, 2012 1 commit