1. 20 Jul, 2019 18 commits
  2. 19 Jul, 2019 4 commits
    • Florian Müllner's avatar
      power: Make sure we fall back to the correct icon · bd516210
      Florian Müllner authored
      Commit bd18313d changed to a new naming scheme for battery icons,
      and used to old icon names as fallback-icon-name for compatibility
      with older/other icon themes.
      
      However that fallback code isn't working correctly, as GThemedIcon's
      default fallbacks will transform a name of `battery-level-90-symbolic`
      to a list of names:
       - `battery-level-90-symbolic`
       - `battery-level-symbolic`
       - `battery-symbolic`
      
      The last one frequently exists, so instead of the intended fallback,
      we end up with a generic battery icon.
      
      Address this by specifying the icon as GIcon instead of an icon-name,
      where we have more control over how the icon is resolved.
      
      #1442
      bd516210
    • Florian Müllner's avatar
      shell: Don't use g_memmove() · 208c5e95
      Florian Müllner authored
      Glib stopped providing any fallback implementations on systems without
      memmove() all the way back in 2013. Since then, the symbol is a simple
      macro around memmove(); use that function directly now that glib added
      a deprecation warning.
      
      !632
      208c5e95
    • Florian Müllner's avatar
      workspacesView: Support horizontal layout · 305e6375
      Florian Müllner authored
      Just as we did for the workspace switcher popup, support workspaces
      being laid out in a single row in the window picker.
      
      Note that this takes care of the various workspace switch actions in
      the overview (scrolling, panning, touch(pad) gestures) as well as the
      switch animation, but not of the overview's workspace switcher component.
      
      There are currently no plans to support other layouts there, as the
      component is inherently vertical (in fact, it was the whole reason for
      switching the layout in the first place).
      
      !575
      305e6375
    • Florian Müllner's avatar
      workspaceSwitcherPopup: Support horizontal layout · ab0f74aa
      Florian Müllner authored
      While mutter supports a variety of different grid layouts (n columns/rows,
      growing vertically or horizontally from any of the four corners), we
      hardcode a fixed vertical layout of a single column.
      
      Now that mutter exposes the actual layout to us, add support for a more
      traditional horizontal layout as well.
      
      !575
      ab0f74aa
  3. 18 Jul, 2019 1 commit
  4. 17 Jul, 2019 1 commit
    • Marco Trevisan's avatar
      extensionPrefs: Inherit from Gtk.Application · b82b553b
      Marco Trevisan authored
      Extension preferences Application class is just a container for a GtkApplication
      so instead of using composition we can inherit from the base GObject class.
      
      Also replace signal connections with vfunc's.
      
      !631
      b82b553b
  5. 16 Jul, 2019 1 commit
  6. 15 Jul, 2019 2 commits
  7. 16 Jul, 2019 1 commit
  8. 15 Jul, 2019 7 commits
    • verdre's avatar
    • verdre's avatar
      iconGrid: Make sure the style is updated before computing the layout · 8f0e9abe
      verdre authored
      In some cases the style-changed signal hasn't been emitted when
      _computeLayout() is called, resulting in the use of the default spacing
      and item size values for the calculations.
      
      One case where this happens is when starting a search. Right after the
      initialization of GridSearchResults, _computeLayout() is called from
      _getMaxDisplayedResults() and the style-changed signal hasn't been
      emitted yet. The computed layout will be wrong and the maximum
      number of results will also be wrong.
      
      To prevent this from happening, make sure the style has been updated
      before doing the calculations in _computeLayout().
      
      !110
      8f0e9abe
    • verdre's avatar
      search: Fix calculation of max number of displayed results for grid · 1a27ff61
      verdre authored
      The calculation of how many results can be shown in GridSearchResults is
      broken: The width of the parent container (resultsView.actor) we're
      using as the maximum width right now is the width of the scrollView of
      SearchResults (which always expands to the whole screen size). This
      width will only be correct if the scrollView (ie. the whole screen) is
      smaller than the max width of searchResultsContent, which only is the
      case for screens smaller than 1000px.
      
      To fix the calculation, use the width of our own actor and don't get it
      using clutter_actor_get_width(), but using the last allocation of the
      actor. This way we don't get the preferred width if the actor is not
      allocated at this point (it's hidden by _ensureProviderDisplay() when
      starting a new search).
      
      Then, when the allocation of the actor changes, rebuild the grid search
      results by calling updateSearch() with the old arguments to ensure the
      number of visible results is correct. The fact that we're only listening
      for allocation changes here is the reason why we never want to use the
      preferred width of the actor inside _getMaxDisplayedResults(): While
      the actor is hidden clutter_actor_get_width() would return the preferred
      width, which we'd then use the as the maximum width. But if the actor
      had a correct allocation before, no notify::allocation signal will be
      emitted when the actor is shown again because the allocation is still
      the same, and we'll end up using the preferred width as maximium width
      forever.
      
      !110
      1a27ff61
    • verdre's avatar
      theme: Don't apply overlap-preventing padding to search results · 3f2cffc2
      verdre authored
      Unlike the app grid, we show the search results while the dash is hidden
      and with a small scrollbar instead of page indicator dots. This
      means there's nothing the search results might horizontally overlap
      with and the padding here is unneccessary.
      
      The spacing between the search results and the screen edges is still
      sufficient because of the paddings applied to searchResultsContent.
      
      On very small screens (< 1000px), this allows the search results to
      utilize a lot more of the horizontal screen space.
      
      !110
      3f2cffc2
    • verdre's avatar
      search: Remove unnecessary containers · a7852705
      verdre authored
      The functionality the searchResultsBin container provides can easily be
      moved into a subclass of St.BoxLayout, no need for an additional StBin.
      The "searchResultsBin" css class isn't used in the stylesheets either.
      
      Same with the scrollChild container.
      
      !110
      a7852705
    • J T's avatar
      Update Karbi translation · a823a213
      J T authored
      a823a213
    • Benjamin Berg's avatar
      shellDBus: Rename ShowMonitorLabels2 to ShowMonitorLabels · 2c8d380e
      Benjamin Berg authored
      The original ShowMonitorLabels has been removed so we can change things
      back to use ShowMonitorLabels again.
      
      !491
      2c8d380e
  9. 14 Jul, 2019 1 commit
  10. 12 Jul, 2019 4 commits