1. 17 May, 2019 3 kayıt (commit)
  2. 16 May, 2019 1 kayıt (commit)
  3. 15 May, 2019 4 kayıt (commit)
  4. 14 May, 2019 1 kayıt (commit)
  5. 03 May, 2019 1 kayıt (commit)
  6. 17 Nis, 2019 1 kayıt (commit)
    • Katarina Behrens's avatar
      Stop qt event loop after KDE settings have been read · 5a64bc2b
      Katarina Behrens yazdı
      Two use-cases here in kde5backend
      1) kde or qt vclplug has already started qt event loop => just use this
      loop to read KDE settings
      2) no qt event loop runs (we're most likely in gtk3_kde5 vclplug) =>
      start a new event loop, read the settings and stop it
      
      In case 2) letting qt event loop run means subsequently all UI ops
      need to happen in main thread. This is problematic to enforce in
      non-qt-based vclplugs
      
      In both cases, cache those settings for future use - the assumption is,
      most of them are static during a session anyway.
      
      Change-Id: Ifa203f4cdb9a753db808f945762fb131ee83393c
      Reviewed-on: https://gerrit.libreoffice.org/70808
      Tested-by: Jenkins
      Reviewed-by: 's avatarThorsten Behrens <Thorsten.Behrens@CIB.de>
      5a64bc2b
  7. 16 Nis, 2019 1 kayıt (commit)
  8. 13 Nis, 2019 2 kayıt (commit)
  9. 04 Nis, 2019 1 kayıt (commit)
  10. 03 Nis, 2019 2 kayıt (commit)
  11. 27 Mar, 2019 1 kayıt (commit)
  12. 24 Mar, 2019 1 kayıt (commit)
  13. 06 Mar, 2019 1 kayıt (commit)
  14. 26 Şub, 2019 1 kayıt (commit)
  15. 13 Şub, 2019 1 kayıt (commit)
  16. 09 Şub, 2019 1 kayıt (commit)
  17. 06 Şub, 2019 1 kayıt (commit)
  18. 04 Şub, 2019 1 kayıt (commit)
  19. 31 Ock, 2019 1 kayıt (commit)
  20. 30 Ock, 2019 1 kayıt (commit)
  21. 28 Ock, 2019 1 kayıt (commit)
  22. 08 Ock, 2019 1 kayıt (commit)
  23. 17 Ara, 2018 1 kayıt (commit)
  24. 01 Ara, 2018 1 kayıt (commit)
  25. 29 Kas, 2018 1 kayıt (commit)
  26. 19 Kas, 2018 1 kayıt (commit)
  27. 05 Kas, 2018 1 kayıt (commit)
  28. 28 Eki, 2018 1 kayıt (commit)
    • Mike Kaganski's avatar
      tdf#120703 PVS: V547 Fix activation of launched process' window · de26ed22
      Mike Kaganski yazdı
      V547 Expression 'procHandle != nullptr' is always false.
      
      The code was nonsensical overall. First, the launched process handle
      was never returned by ShellExecuteExW, because SEE_MASK_NOCLOSEPROCESS
      wasn't used, so GetProcessId couldn't succeed. Then, nullptr window
      handle was passed to GetWindowThreadProcessId, thus never returning a
      meaningful result.
      
      This reimplements this to find the launched process' main window by
      first waiting for process idle (up to 1-second delay is possible),
      then enumerating all the top-level windows and checking their process.
      
      Change-Id: I5fb4c04147b3f9414e27650a023f7844523c18bd
      Reviewed-on: https://gerrit.libreoffice.org/62478
      Tested-by: Jenkins
      Reviewed-by: 's avatarMike Kaganski <mike.kaganski@collabora.com>
      de26ed22
  29. 26 Eki, 2018 1 kayıt (commit)
  30. 24 Eki, 2018 1 kayıt (commit)
  31. 22 Eki, 2018 1 kayıt (commit)
  32. 19 Eki, 2018 1 kayıt (commit)
  33. 09 Eki, 2018 1 kayıt (commit)