1. 09 Jul, 2018 1 commit
  2. 02 Jul, 2018 2 commits
  3. 16 Jan, 2018 2 commits
    • Daniel Vrátil's avatar
      Don't create multiple in-process backend instances · 6e37f303
      Daniel Vrátil authored
      The 'name' argument is in most cases empty by which the caller indicates that
      they want the default backend. As such repeated calls to loadBackendInProcess(QString())
      cause to instantiate a new backend every time, because the name check in the
      condition is never true.
      Reviewers: sebas, davidedmundson
      Reviewed By: davidedmundson
      Subscribers: plasma-devel
      Tags: #plasma
      Differential Revision: https://phabricator.kde.org/D9905
    • Daniel Vrátil's avatar
      Wayland: don't share the same Config between backend and clients · 4abdc5b1
      Daniel Vrátil authored
      Sharing a single config leads to undesired side-effects. The GetConfigOperation
      is assumed to always return a new copy of the current config that is not changed
      unless registered to ConfigMonitor. When sharing a single copy this assumption is
      broken which leads to misbehaviour in KDED.
      This change makes GetConfigOperation always return a new copy of the config that
      caller can register to ConfigMonitor if they want to, otherwise it remains
      unchanged until released.
      Reviewers: sebas, davidedmundson
      Reviewed By: sebas
      Subscribers: plasma-devel
      Tags: #plasma
      Differential Revision: https://phabricator.kde.org/D9904
  4. 30 Oct, 2017 1 commit
  5. 28 Jul, 2016 1 commit
  6. 27 Jul, 2016 1 commit
  7. 02 Jun, 2016 1 commit
  8. 29 Apr, 2016 1 commit
  9. 07 Apr, 2016 1 commit
    • Sebastian Kügler's avatar
      Allow preferring a specific backend in backendloader · d7f78c2f
      Sebastian Kügler authored
      The name argument to loadBackendPlugin is used from the external backend
      launcher, but was not considered when loading the backend plugin. That
      means that loading the Fake backend using the out-of-process mechanism
      failed, since the backend isn't passed and the runtime-detected plugin
      would be loaded - that's never the Fake backend.
      This patch passes the name argument into preferredBackend, and if
      supplied, it's the preferred filter for the installed backend list.
      Test Plan:
      * added autotest
      * ran kscreen_backend_launcher Fake" on the command line, verified that
        the Fake backend is loaded
      Reviewers: graesslin
      Reviewed By: graesslin
      Subscribers: broulik
      Differential Revision: https://phabricator.kde.org/D1325
  10. 18 Mar, 2016 2 commits
  11. 17 Mar, 2016 1 commit
  12. 15 Mar, 2016 5 commits
    • Sebastian Kügler's avatar
      Consider the case where KSCREEN_BACKEND_INPROCESS=false · de4ed68c
      Sebastian Kügler authored
      Introduce "expected behavior when reading this env var.
    • Sebastian Kügler's avatar
      backendloader defaults to in-process loading unless x11 · df36ad46
      Sebastian Kügler authored
      This change prefers the in-process mode to be used for all backends,
      except XRandr. The KSCREEN_BACKEND_INPROCESS env var still bears highest
      priority, but if it's not specified, we'll now use the in-process mode
      by default for wayland, qscreen and fake backends, since these are
      considered safe (enough) for in-process operation.
    • Sebastian Kügler's avatar
      document fallback · 30acc528
      Sebastian Kügler authored
    • Sebastian Kügler's avatar
      backendmanager falls back to QScreen backend · 5077ee8a
      Sebastian Kügler authored
      Fall back to QScreen backend if the backend can't be found otherwise
    • Sebastian Kügler's avatar
      Refactor the backend loading code · e020fe72
      Sebastian Kügler authored
      Untangle the large plugin loading logic in the BackendManager static
      into  separate bits. This makes the code clearer and easier to auto-test.
      - listBackends() compiles a list of backends from the plugin paths
      - preferredBackend() picks the backend, in this priority:
      	- if KSCREEN_BACKEND is set in the environment, this is the only
      	  used method to find the backend plugin
      	- if platform is X11, the XRandR backend is picked
              - if platform is wayland, KWayland backend is picked
              - if neither is the case, QScreen backend is picked
      It does introduce a slight behavioral change: The mechanism was based on
      falling through, so it would consider another backend if the logically
      picked on fails to load. This is undesired behavior, however, since the
      backendloader may be able to load the plugin, but that doesn't mean that
      the plugin actually work.
      Parsing of the KSCREEN_BACKEND variable is kept case-insensitive.
  13. 11 Mar, 2016 1 commit
  14. 07 Mar, 2016 5 commits
  15. 15 Dec, 2015 1 commit
  16. 26 Nov, 2015 1 commit
    • Sebastian Kügler's avatar
      add debug · 97b6b828
      Sebastian Kügler authored
      Add a few tests to find out when exactly we're creating new config (or
      when we should do that)
  17. 24 Nov, 2015 13 commits