1. 17 May, 2019 3 commits
  2. 16 May, 2019 3 commits
  3. 15 May, 2019 14 commits
  4. 14 May, 2019 1 commit
  5. 12 May, 2019 1 commit
  6. 11 May, 2019 1 commit
  7. 09 May, 2019 5 commits
  8. 08 May, 2019 1 commit
  9. 07 May, 2019 3 commits
    • Florian Müllner's avatar
      st: Delay handling of :first/:last-child changes · 0afd600e
      Florian Müllner authored
      Updating the :first/:last-child pseudo classes can result in a lot
      of unnecessary style changes when bulk-adding children to a container,
      as every child ends up as the new last child.
      
      Address this by deferring the style change to an idle, so we only do
      the work once for the actual first and last child.
      
      GNOME/gnome-shell!529
      0afd600e
    • Florian Müllner's avatar
      Revert "st: Reload icon on style changes only if necessary" · 598407b1
      Florian Müllner authored
      The size isn't the only relevant style change, we also need to pick
      up icon-colors, icon-style and icon-shadow.
      
      This reverts commit 94995e9c.
      
      GNOME/gnome-shell!529
      598407b1
    • Fabrice Bellet's avatar
      network: Handle interface name changes · d9bfa16f
      Fabrice Bellet authored
      The interface name when a device is added may not be the final one. For
      example when using USB tethering, it will first appear as 'usb0' before
      being renamed to something like 'enp0s20f0u1' depending on the port the
      phone is plugged in.
      
      As a result, we will ignore the new interface name in that case and fail
      to associate the correct connection with the device: Instead of the
      correct "USB Ethernet" (or user-customized name), it will show up as
      "Ethernet".
      
      Fix this by updating names and connections when a device's interface
      property changes.
      
      GNOME/gnome-shell!534
      d9bfa16f
  10. 04 May, 2019 2 commits
    • Dylan McCall's avatar
      panel: Drag topmost maximized window · 03117d65
      Dylan McCall authored
      This makes it possible to drag a window which appears connected with the
      panel, even if it is not in focus. As a result, it should be easier to
      manipulate side-by-side windows.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=679290
      03117d65
    • Florian Müllner's avatar
      texture-cache: Keep aspect ratio for content images · 5520bb38
      Florian Müllner authored
      Images are loaded either with a supplied fixed size, or using the "native"
      dimensions of the file. When creating a content image from the loaded data,
      we currently simply apply this directly to the preferred size.
      
      This works usually fine: GdkPixbuf will always keep the aspect ratio, so
      if only one dimension is provided, the other will be adjusted accordingly:
      
      Loading a 200x200 image with a requested size of (100, -1) will result in
      a 100x100 content image.
      
      There is a catch though: GdkPixbuf will only scale *down* to the requested
      size, no up. That is, loading a 100x100 image with a requested size of
      (200, -1) will result in a 100x100 pixbuf. But as we assume that the pixbuf
      size matches the requested size, the image content ends up with 200x100.
      
      Fix this by explicitly handling the case where only one size was supplied,
      and make the other dimension take the aspect ratio into account
      
      GNOME/gnome-shell!525
      5520bb38
  11. 03 May, 2019 3 commits
  12. 02 May, 2019 1 commit
  13. 01 May, 2019 1 commit
  14. 30 Apr, 2019 1 commit
    • Florian Müllner's avatar
      dashSpacer: Don't trigger allocations from size negotiations · d5ebd8c8
      Florian Müllner authored
      If an actor's allocation is outdated, clutter_actor_get_allocation_box()
      will queue a relayout. That's why it's advised to not use the function
      unless the allocation is known to be valid (namely during paint), but
      in particular not from within get_preferred_width/height vfuncs.
      
      Using the :allocation property (which may be outdated) would be better,
      but in this case we can simply delegate the request to the correct actor.
      
      GNOME/gnome-shell#1065
      d5ebd8c8