1. 10 Sep, 2018 1 commit
  2. 23 Feb, 2018 1 commit
  3. 12 Feb, 2018 1 commit
  4. 11 Feb, 2018 1 commit
  5. 23 Jan, 2018 2 commits
  6. 22 Jan, 2018 1 commit
  7. 25 Oct, 2016 3 commits
  8. 24 Apr, 2016 1 commit
  9. 30 Jan, 2016 1 commit
  10. 26 Dec, 2014 1 commit
  11. 07 Nov, 2014 1 commit
  12. 30 Sep, 2014 1 commit
  13. 03 Sep, 2014 1 commit
  14. 22 Aug, 2014 1 commit
  15. 24 May, 2014 1 commit
  16. 26 Oct, 2013 4 commits
    • Abdo Roig-Maranges's avatar
      get rid of tracking adjustments · 9367d646
      Abdo Roig-Maranges authored
      They are not used anywere, and do not seem to become useful anymore in
      the light of the new separation of document and view.
    • Abdo Roig-Maranges's avatar
      adapt view_adjustment callbacks to new document/view separation · 36346362
      Abdo Roig-Maranges authored
      The adjustment callbacks act as an interface between position data in
      the document object, and the adjustments.
      We remove the horizontal centering code, as now it is done by
      position_set. Those callbacks should not change the position read from
      the document object in any way.
      Also, we split the adjustment_value_changed callback into a vertical and
      an horizontal version. Previously a single callback was reused for both,
      horizontal and vertical. That lead to a subtle problem when coming out
      of index mode. What happened was the following:
        1. horizontal adjustment bounds change coming out of index mode. This
           triggers an hadjustment changed signal.
        2. the hadjustment_changed callback handles it, and resets the
           hadjustment value, as the bound may have changed. This triggers a
           value_changed event.
        3. the value_changed callback handles the event, and captures the
           position for *BOTH*, horizontal and vertical adjustments, saving
           them to the document object.
        1..3 is repeated for the vertical adjustment.
        Now, if in 3. the horizontal adjustment bounds were not yet updated
        after the index mode, we got ourselves at the wrong vertical position.
      This race condition is avoided now because both value_changed callbacks
      *ONLY* handle their own direction, either vertical or horizontal, not
    • Abdo Roig-Maranges's avatar
      add a custom refresh-view signal · 692e72ab
      Abdo Roig-Maranges authored
      Now we can trigger a gtk page refresh calling refresh_view. This
      function triggers a custom signal refresh-view, whose handler copies the
      position from the document object to the adjustments.
    • Abdo Roig-Maranges's avatar
      merge callbacks for pages-per-row, first-page-column and page-padding · 0da491f7
      Abdo Roig-Maranges authored
      All of those callbacks are conceptually related (change the page
      layout), and depend from one another.
      Now the single callback page_layout_value_changed defers to
      page_widget_set_mode to change whatever is needed in the GTK widgets.
  17. 31 Aug, 2013 1 commit
  18. 23 Mar, 2013 1 commit
    • Benoît Knecht's avatar
      Use signals to readjust_view_after_zooming() · c9eef954
      Benoît Knecht authored
      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's avatarSebastian Ramacher <sebastian+dev@ramacher.at>
  19. 07 Dec, 2012 1 commit
  20. 01 Aug, 2012 1 commit
    • Abdó Roig-Maranges's avatar
      Added option to recolor keeping hues of original color. · c57463a0
      Abdó Roig-Maranges authored
      If option recolor-keephue is true, the recoloring algorithm
      only adjusts the lightness of the original color, keeping the
      rest of the properties close to the original.
      When recolor-keephue is set to false, the recoloring is performed
      as it was before, interpolating linearly between recolor-lightcolor
      and recolor-darkcolor except for a different weighting for the
      lightness which is closer to perception.
      Signed-off-by: Sebastian Ramacher's avatarSebastian Ramacher <sebastian+dev@ramacher.at>
  21. 27 Jun, 2012 1 commit
  22. 01 May, 2012 1 commit
  23. 27 Mar, 2012 1 commit
  24. 14 Mar, 2012 1 commit
  25. 07 Mar, 2012 1 commit
  26. 09 Feb, 2012 1 commit
  27. 08 Feb, 2012 3 commits
  28. 07 Feb, 2012 2 commits
  29. 09 Dec, 2011 1 commit
  30. 20 Nov, 2011 1 commit
  31. 23 Oct, 2011 1 commit