Re: Static code analysis - the easiest way to improve

2016-02-28 Thread Frederik Schwarzer
Am Sonntag, 28. Februar 2016, 20:18:22 schrieb Nick Shaforostoff: > > > Let us know in this thread if code you're interested in isn't > > > there.> > > Could we have kdegames there? > > ok, i'll include them in the next build (in a week or so) Thank you. _

Re[2]: Static code analysis - the easiest way to improve

2016-02-28 Thread Nick Shaforostoff
> To be honest, I've tried to use it many times, but I always seem to > end up diving in warnings in other projects. It's hard to filter for > projects I have a grasp on. > > How do you deal with this? i just sort by filepath/name (the column is on the right, you need to scroll horizontally to g

Re: Static code analysis - the easiest way to improve

2016-02-28 Thread Jaroslaw Staniek
On 28 February 2016 at 20:21, Aleix Pol wrote: > On Sun, Feb 28, 2016 at 3:59 PM, Jaroslaw Staniek wrote: > > Hi, > > Just to remind. If someone has some time to fix bugs, KDE > > apps/Calligra/Frameworks static analysis is the easiest way to improve > > Calligra. > > Code defects are well expla

Re: Static code analysis - the easiest way to improve

2016-02-28 Thread Aleix Pol
On Sun, Feb 28, 2016 at 3:59 PM, Jaroslaw Staniek wrote: > Hi, > Just to remind. If someone has some time to fix bugs, KDE > apps/Calligra/Frameworks static analysis is the easiest way to improve > Calligra. > Code defects are well explained (like uninitialized variables or > NULL-related failures

Re[2]: Static code analysis - the easiest way to improve

2016-02-28 Thread Nick Shaforostoff
> > Let us know in this thread if code you're interested in isn't there. > Could we have kdegames there? ok, i'll include them in the next build (in a week or so) ___ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/lis

Re: Static code analysis - the easiest way to improve

2016-02-28 Thread Frederik Schwarzer
Am Sonntag, 28. Februar 2016, 15:59:46 schrieb Jaroslaw Staniek: Hi, > Let us know in this thread if code you're interested in isn't there. Could we have kdegames there? Regards, Frederik ___ calligra-devel mailing list calligra-devel@kde.org https://

[Differential] [Updated] D1032: Make KUndo2Stack::push return false if the command was merged (and deleted) rather than pushed

2016-02-28 Thread Jarosław Staniek
staniek added reviewers: kossebau, rempt, boemann, aspotashev. staniek added a subscriber: Calligra-Devel-list. REPOSITORY rCALLIGRA Calligra REVISION DETAIL https://phabricator.kde.org/D1032 EMAIL PREFERENCES https://phabricator.kde.org/settings/panel/emailpreferences/ To: staniek, kosse

Re: Static code analysis - the easiest way to improve

2016-02-28 Thread Jaroslaw Staniek
On 28 February 2016 at 15:59, Jaroslaw Staniek wrote: > Hi, > Just to remind. If someone has some time to fix bugs, KDE > apps/Calligra/Frameworks static analysis is the easiest way to improve > Calligra. > Code defects are well explained (like uninitialized variables or > NULL-related failures).

Re: Static code analysis - the easiest way to improve

2016-02-28 Thread Jaroslaw Staniek
On 28 February 2016 at 16:21, Frederik Schwarzer wrote: > Am Sonntag, 28. Februar 2016, 15:59:46 schrieb Jaroslaw Staniek: > > Hi, > > > Let us know in this thread if code you're interested in isn't there. > > Could we have > ​​ > kdegames there? > > ​Good idea, CC'd Nick as he updates the builds

Re: Static code analysis - the easiest way to improve

2016-02-28 Thread Jaroslaw Staniek
On 28 February 2016 at 16:26, Tomas Mecir < ​​ mec...@gmail.com> wrote: > Well, I'd like to, but when I log in and try to access the KDE stuff, > I can see the summary, but accessing the actual defect list gives me a > red box with this: > > It may take a few minutes before you can view your defec

Re: Static code analysis - the easiest way to improve

2016-02-28 Thread Tomas Mecir
Well, I'd like to, but when I log in and try to access the KDE stuff, I can see the summary, but accessing the actual defect list gives me a red box with this: It may take a few minutes before you can view your defects, when you change your email or password or sign-in with Github for the first ti

Static code analysis - the easiest way to improve

2016-02-28 Thread Jaroslaw Staniek
Hi, Just to remind. If someone has some time to fix bugs, KDE apps/Calligra/Frameworks static analysis is the easiest way to improve Calligra. Code defects are well explained (like uninitialized variables or NULL-related failures). Much easier than actually reading that bug reports, analysing them

Re: Review Request 125485: Unselect text when the text tool is deactivated.

2016-02-28 Thread Camilla Boemann
--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/125485/#review92851 --- I'd prefer if this doesn't go in In words at least it's on pu

Re: Review Request 125485: Unselect text when the text tool is deactivated.

2016-02-28 Thread David Faure
> On Oct. 3, 2015, 10:02 a.m., Camilla Boemann wrote: > > ahh - well i still think the solution is wrong and i am in berlin for the > > qt world summit so no near my home computer, but will take a look when I > > get a chance Ping? This issue is still there. - David ---