1. 20 Mar, 2019 5 commits
    • Benjamin Berg's avatar
      display: Only enforce single mode when desired by UI · e387b3bb
      Benjamin Berg authored
      We should only enforce single mode, when we have exactly two monitors
      and the two button UI is used to switch between them in single mode.
      Move the code to ensure the single configuration into the relevant
      callback handler, rather than trying to solve this globally.
    • Benjamin Berg's avatar
      display: Make rebuilding variable a counter · 98d20659
      Benjamin Berg authored
      We need to also set rebuilding while updating some other UI elements.
      Make it into a counter to allow for recursive setting.
      Note that additional checks for rebuilding will be added in later
    • Benjamin Berg's avatar
      display: Reset resolution when switching configuration types · 21bb6416
      Benjamin Berg authored
      It generally makes more sense to reset the resolution of a monitor after
      we switch configuration types. The main case where this is relevant is
      switching from a mirror configuration (CLONE) to either join or single.
      In this case, higher resolutions for monitors may become available.
      Note that this might be annoying to some users, because there may be
      monitors reporting a lower "preferred" resolution than the highest
      supported resolution. There is little we can do though, as always
      selecting the highest resolution doesn't seem like a much better
    • Benjamin Berg's avatar
      display: Prevent error when serializing invalid configuration · ae22f72c
      Benjamin Berg authored
      If no monitors are enabled, then the variant would end up with an
      invalid variant type, causing a crash later on. This case only happened
      due to other bugs (i.e. in principle we should never send a
      configuration without any monitors to the server).
      Prevent the serialization error by specifying the correct type for the
      builder, therefore potentially preventing a crash in such a corner case.
    • Benjamin Berg's avatar
      display: Ensure we have a primary monitor after all were disabled · 0c4e84e4
      Benjamin Berg authored
      When enabling the first monitor, we need to select it as primary as we
      otherwise end up without a primary monitor (rendering the configuration
      invalid). "Unsetting" the NULL primary monitor effectively causes the
      first and only available monitor to become the primary, while not doing
      anything if we have a primary monitor.
  2. 18 Mar, 2019 4 commits
    • Benjamin Berg's avatar
      display: Enable all monitors when switching to join config · 20d24992
      Benjamin Berg authored
      The new code had a bug in that it only ever enabled the first monitor
      rather than all usable ones. Fix this by removing the erroronuous break.
      Also clarify the comment a bit that the current solution is not really
      ideal as it may result in invalid configurations (i.e. we enable more
      outputs than are possible with the number of available CRTCs).
      Fixes #418
    • Alan Mortensen's avatar
      Updated Danish translation · c8ffb340
      Alan Mortensen authored
    • Robert Ancell's avatar
      applications: Fix flatpak ID memory leak · 29eebced
      Robert Ancell authored
    • Marco Trevisan's avatar
      display: Don't always set the primary monitor to the first in list · 49957ef8
      Marco Trevisan authored
      As per the binding that we have between the list store and the combo-box, when
      the first element is added to the list-store, the combo box set this value as
      the selected-index, and this leads to a call to cc_display_monitor_set_primary
      which set the first-listed monitor as primary and unset the real primary monitor.
      To avoid this, just ignore the binding when rebuilding the UI, since in this
      phase control-center should just reflect the actual state without changing
      Fixes #419
  3. 17 Mar, 2019 1 commit
  4. 16 Mar, 2019 1 commit
  5. 15 Mar, 2019 1 commit
  6. 13 Mar, 2019 9 commits
  7. 11 Mar, 2019 14 commits
  8. 09 Mar, 2019 3 commits
  9. 07 Mar, 2019 2 commits