> On Oct. 31, 2011, 7:43 p.m., Dmitry Kazakov wrote:
> > Thanks for the fix! =)
> > Just two small things:
> > 1) I think it would be logical to reset the stroke id right after
> > endStroke(m_strokeId) in mouseReleaseEvent() function. Like:
> >image->endStroke(m_strokeId);
> >m_strokeI
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/102552/#review7861
---
please close this review
- C. Boemann
On Sept. 24, 2011, 1:28
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/102790/#review7862
---
please close this review
- C. Boemann
On Oct. 6, 2011, 1:11 p
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/100716/#review7863
---
Hi i removed this class completely now, so please close the revi
> On Nov. 1, 2011, 9:41 p.m., Dmitry Kazakov wrote:
> > The bug is a really good catch! I didn't even think about it. =)
> >
> > But the problem is, this very solution will not work, I'm afraid. There is
> > a couple of problems.
> > 1) setDirty() and refreshGraphAsync() do different things act
Oh and for sake of consitency, shouldn't we rename calligra-chart, calligra-
common, calligra-formula and calligra-services ?
On Monday 31 October 2011, C. Boemann wrote:
> Hi
>
> I've changed all those calligra-product to calligraproduct in bugzilla so
> they match our application names. And cal
