> Romano, Denis, I think this issue has been fixed in next. Immi was very
> good at fixing it. But I have not had time to test it, so I'll
> appreciate it if you let us know if the bug has been addressed.
I think I took a look a long while ago and it was ok. I just looked
again at the patch to xo
Denis Auroux twisted the bytes to say:
Denis> Hi Romano,
Denis> I'm happy to take a look at the xoj file (no need to send the pdf) even
though I'm not directly involved in
Denis> xournal-next. Daniel (cc-ed) might also appreciate a copy. With your
permission, if this is related as I suspe
On 09/10/16 14:13, Immi Halupczok wrote:
> Ok, I found the bug. It has nothing to do with the -nan; instead, the
> problem is that my code doesn't handle fixed-width strokes properly.
> I'll fix it in a minute.
>
> Immi
Hi, has the fix been pushed/integrated in xournal-next? Because I
Am 09.10.2016 um 00:55 schrieb D M German:
> Immi Halupczok twisted the bytes to say:
>
>
> Immi> Concerning -nan:
> Immi> I can confirm that normal xournal doesn't crash, next does. And I just
> Immi> tried: line-widths-optimized does not crash. (So chances are smaller
> Immi> that it's my
Immi Halupczok twisted the bytes to say:
Immi> Concerning -nan:
Immi> I can confirm that normal xournal doesn't crash, next does. And I just
Immi> tried: line-widths-optimized does not crash. (So chances are smaller
Immi> that it's my fault ;-) )
Immi
It was :)
it crashes here
Concerning -nan:
I can confirm that normal xournal doesn't crash, next does. And I just
tried: line-widths-optimized does not crash. (So chances are smaller
that it's my fault ;-) )
Immi
Am 06.10.2016 um 20:01 schrieb dmg:
> This is the stroke that is crashing xournal:
>
>
> -nan -na
I fixed the two-equal-points-crashes-xournal bug (in my repository,
branch line-widths-optimized). I did not yet do anything about the
"-nan" issue.
Immi
Am 06.10.2016 um 20:51 schrieb Denis Auroux:
> Interesting. Neither of the issues causes the stable/upstream xournal to
> crash, thou
