1. 27 Jul, 2022 9 commits
    • ivan tkachenko's avatar
      effects/overview: Fix anchor on a placeholder message · 7b24df24
      ivan tkachenko authored
          ScreenView.qml:202:17: Unable to assign QQuickItem to QQuickAnchorLine
    • Vlad Zahorodnii's avatar
    • Vlad Zahorodnii's avatar
      Drop Platform::enabledOutputs() · a1985168
      Vlad Zahorodnii authored
      At the moment, a platform should provide two output lists - one that
      lists all available outputs, and the other one that contains only
      enabled outputs. In general, this amounts to some boilerplate code and
      forces backends to be implemented in some certain way, which sometimes
      is inconvenient, e.g. if an output is disabled or enabled, it will be
      simpler if we only change Output::isEnabled(), otherwise we need to
      start accounting for corner cases such as the order in which
      Output::isEnabled() and Platform::enabledOutputs() are changed, etc.
    • Vlad Zahorodnii's avatar
      Make outputs disabled by default · 2629007e
      Vlad Zahorodnii authored
      This can be used to make our backends more multi-purpose. At the moment,
      new outputs are enabled by default, but it makes sense to do otherwise.
      For example, if an output is disabled by default, it would be possible
      to delegate initial output configuration to layer above, to kwin.
      In long term, the drm backend would need to scan connectors, create an
      Output for every one of them, kwin sees new outputs and tries to apply
      the initial output configuration, which includes the enabled status.
    • ivan tkachenko's avatar
      Mark window type properties as CONSTANT · 854aebb3
      ivan tkachenko authored
      Since we don't have any means of getting notified by _NET_WM when a
      windowType changes, and since KWin would handle that quite poorly, AND
      since no one does that in real-world applications anyway, we might as
      well mark those getters as CONSTANT, so that QML engine would stop
      complaining about depending on non-NOTIFYable properties.
      According to the specification, the window type should be decided before
      a window gets mapped.
    • David Edmundson's avatar
      Ensure size is valid after maximising · 2073415f
      David Edmundson authored and Vlad Zahorodnii's avatar Vlad Zahorodnii committed
      In X11 when a window is maximised if the client is unable to fufill the
      space provided we centre align the window.
      With the new floating point geometry behaviour of centreing changes.
      Instead of a 1 pixel gap at the top, we get a 0.5 pixel gap either side.
      When we get into the codepath to "fix" the window in `closeHeight` we
      only move the top, giving us an invalid buffer size.
      We don't really want to change the logic here; on xwayland with the
      scaling opt-out path it's feasible for a floating sized logical size to
      still be representable. This code rounds to the native unit after all
      the logic has taken effect.
    • Alexey Andreyev's avatar
      kwinglutils: restore alignment logic for Mali GPU · c61515cd
      Alexey Andreyev authored and Vlad Zahorodnii's avatar Vlad Zahorodnii committed
      Contributes to:
    • Vlad Zahorodnii's avatar
      Make OutputConfiguration take OutputMode · 3ce24a0c
      Vlad Zahorodnii authored
      OutputMode provides a more robust way to refer to outputs. A mode can
      have flags and things as such that are not taken into account with mode
      + refresh rate.
    • Vlad Zahorodnii's avatar
      effects/slidingpopups: Fix slide offset · 726f97d2
      Vlad Zahorodnii authored
      Code such as "screenRect.bottom() - windowGeo.bottom()" assumes that
      both screenRect and windowGeo have the same type. At the moment, it's
      not the case, screenRect has QRect type and windowGeo has QRectF type,
      so the calculated offset will be off by one.
  2. 26 Jul, 2022 10 commits
  3. 25 Jul, 2022 5 commits
  4. 24 Jul, 2022 16 commits