1. 21 Feb, 2015 1 commit
  2. 23 Jan, 2015 1 commit
  3. 12 Jan, 2015 1 commit
  4. 02 Jan, 2015 3 commits
  5. 28 Nov, 2014 1 commit
  6. 10 Nov, 2014 1 commit
  7. 31 Oct, 2014 1 commit
  8. 30 Oct, 2014 1 commit
  9. 29 Oct, 2014 1 commit
  10. 26 Oct, 2014 2 commits
  11. 17 Sep, 2014 1 commit
    • Martin Walch's avatar
      reformat whole code base of Kalzium · 7adfaccb
      Martin Walch authored
      Across the project there are many coding styles with lots of different
      indentation patterns. There are three different tabs to space
      conversions (1:2, 1:4, 1:8), even mixed within individual files. This
      makes the code unnecessarily hard to read and to edit.
      
      In the hope that I do not offend anybody: unify code style.
      
      Roughly apply the style from kdelibs:
      
      * get rid of all tabs
      * indentation is four spaces
      * unify includes and include guards
      * less blank lines
      * one space after "if", "for", etc.
      * no space after cast
      * prefix operators ("++", "--") instead of postfix where applicable
      * pointers: preferably single space before "\*" (same for "&")
      * opening curly braces on same line except for implementations
      * no whitespace after opening parenthesis "(" or before closing ones ")"
      * no single line "if", "for", "else", etc. (always curly braces)
      * indent "case" to same level as corresponding "switch"
      * at least in some files adjust line wraps to a limit of 100 chars
      * exactly one newline at EOF
      
      Also some formatting to copyright statements (I hope this is legally ok)
      
      Additionally:
      * fix some spelling errors
      * constify& some foreach loops (suggested by krazy2)
      * replace some single char strings with chars (suggested by krazy2)
      
      This whole patch fixes between 15 and 20 krazy2 warnings.
      
      REVIEW: 120238
      7adfaccb
  12. 15 Sep, 2014 2 commits
    • Martin Walch's avatar
      Fix bug #338666: "Kalzium crashes when selecting >File >Export Data..." · 7c590a04
      Martin Walch authored
      Problem is easy to spot with valgrind:
      The private ExportDialog *m_exportDialog is not explicitely initialized
      with 0, so later calling "if (!m_exportDialog)" may fail.
      
      This accidentally slipped in with a header cleanup (commit d36687d5...)
      
      Easy fix: initialize the pointer with 0 just like all the others.
      
      REVIEW: 120219
      7c590a04
    • Martin Walch's avatar
      Fix bug #338666: "Kalzium crashes when selecting >File >Export Data..." · 287791bb
      Martin Walch authored
      Problem is easy to spot with valgrind:
      The private ExportDialog *m_exportDialog is not explicitely initialized
      with 0, so later calling "if (!m_exportDialog)" may fail.
      
      This accidentally slipped in with a header cleanup (commit d36687d5...)
      
      Easy fix: initialize the pointer with 0 just like all the others.
      
      BUG: 338666
      FIXED-IN: 4.14.2
      287791bb
  13. 04 Aug, 2014 2 commits
  14. 31 Jul, 2014 4 commits
  15. 25 Jul, 2014 2 commits
  16. 24 Jul, 2014 2 commits
  17. 21 Jul, 2014 1 commit
  18. 20 Jul, 2014 1 commit
  19. 16 Jul, 2014 1 commit
  20. 07 Jul, 2014 1 commit
  21. 05 Jul, 2014 1 commit
  22. 30 Jun, 2014 1 commit
  23. 28 Jun, 2014 1 commit
  24. 24 Jun, 2014 1 commit
  25. 23 Jun, 2014 1 commit
  26. 21 Jun, 2014 1 commit
  27. 19 Jun, 2014 1 commit
  28. 15 Jun, 2014 1 commit
  29. 25 May, 2014 1 commit
  30. 28 Apr, 2014 1 commit