1. 31 Oct, 2014 1 commit
  2. 30 Oct, 2014 1 commit
  3. 29 Oct, 2014 1 commit
  4. 26 Oct, 2014 2 commits
  5. 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
  6. 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
  7. 04 Aug, 2014 2 commits
  8. 31 Jul, 2014 4 commits
  9. 25 Jul, 2014 2 commits
  10. 24 Jul, 2014 2 commits
  11. 21 Jul, 2014 1 commit
  12. 20 Jul, 2014 1 commit
  13. 16 Jul, 2014 1 commit
  14. 07 Jul, 2014 1 commit
  15. 05 Jul, 2014 1 commit
  16. 30 Jun, 2014 1 commit
  17. 28 Jun, 2014 1 commit
  18. 24 Jun, 2014 1 commit
  19. 23 Jun, 2014 1 commit
  20. 21 Jun, 2014 1 commit
  21. 19 Jun, 2014 1 commit
  22. 15 Jun, 2014 1 commit
  23. 25 May, 2014 1 commit
  24. 28 Apr, 2014 1 commit
  25. 16 Mar, 2014 1 commit
  26. 10 Mar, 2014 1 commit
    • Etienne Rebetez's avatar
      REVIEW: 116638 · 66984992
      Etienne Rebetez authored
      Use EIGEN3 instead of EIGEN2.
      Thanks to Maximiliano Curia for the patch.
      66984992
  27. 28 Dec, 2013 1 commit
    • Yichao Yu's avatar
      Update min and max value at the same time in order to be more friendly with... · f0778889
      Yichao Yu authored
      Update min and max value at the same time in order to be more friendly with typing in the min/max box
      
      REVIEW: 114006
      
      This patch makes the behavior while typing in the min/max boxes more friendly.
      
      Currently if one types in the maximum value box, the minimum value will stuck at a small value due to the small value in the maximum value box before one finish typing. (I don't really call this a bug, but I think it is not friendly.)
      
      This patch tries to update both the maximum and minimum values whenever one of them changes (in the right order to always respect the one that changes) so that the actual range displayed is always the closed possible to the input values. It also covers the cases when min/max values change from illegal values to legal values (max > min) in some other ways.
      f0778889
  28. 27 Nov, 2013 1 commit
  29. 30 Oct, 2013 1 commit
  30. 29 Oct, 2013 2 commits
  31. 26 Oct, 2013 1 commit