GitLab Commit is coming up on August 3-4. Learn how to innovate together using GitLab, the DevOps platform. Register for free:

  1. 08 Jun, 2021 3 commits
  2. 05 Jun, 2021 1 commit
  3. 02 Jun, 2021 10 commits
  4. 26 May, 2021 2 commits
  5. 16 Feb, 2021 1 commit
  6. 13 Feb, 2021 3 commits
  7. 07 Feb, 2021 2 commits
  8. 23 Jan, 2021 2 commits
    • David Rubio's avatar
      Merge branch 'edid-string' into 'master' · 86c46bbb
      David Rubio authored
      Use std::string for EDID parsing
      See merge request !25
    • Roman Gilg's avatar
      fix: use std::string for EDID parsing · 0e9309d2
      Roman Gilg authored
      The previous QString lead to compile issues because of using a deleted QChar
      constructor. Fix this by just using std::string with better API.
      Since std::string is not as feature-rich we have to cleanup the string we
      read in ourselves though. Do this through two simple loops removing trailing
      whitespace and cutting the string off at a line break.
  9. 09 Dec, 2020 3 commits
  10. 01 Dec, 2020 5 commits
  11. 30 Nov, 2020 3 commits
    • David Rubio's avatar
      test: make tests expect the preferred mode · 112cf9f4
      David Rubio authored
      After the last commit that changed the auto mode to preferred mode,
      tests were failing due to them expecting the highest mode instead
      of the preferred mode as specified on the config.
      This changes it so the tests expect the correct value we're giving
      it from Output::auto_mode()
    • David Rubio's avatar
      fix(lib): pick preferred mode instead of highest · b8a47d0a
      David Rubio authored
      This causes issues for monitors that advertise preferred modes
      lower than the highest available monitor (say, give a 165Hz mode,
      but prefer 144Hz while 165Hz is "overclocking"). This isn't exactly
      a edge case nowadays, so this commit just picks the preferred
      mode as advertised by the monitor, instead of the highest
      available one, which *could* cause problems.
      This also causes issues with CRTs, specially 640x480 CRTs usually
      advertise 800x600 modes that look a little blurry or garbled.
      I'm fairly sure no one uses a 640x480 CRT in 2020[1], but who
    • David Rubio's avatar
      fix(randr): skip DoubleScan modes · 5eb6392e
      David Rubio authored
      This causes issues such as #32, and xrandr itself does filter
      them since 2008 (!), so it's probably good practice to skip
      DoubleScan (32) modes, as they're useless in modern monitors.
  12. 17 Oct, 2020 2 commits
  13. 16 Oct, 2020 3 commits