Doublonmousse

I've started to debug print and add artificial delays to the input function. As expected, this function is blocking meaning if it takes longer than a frame the fps drops....

Well I thought it was that but it seemingly isn't (it could very well cause lag but seemingly not cause the "curves are line" scenario). Tested only on windows though...

> Maybe it has something to do with the path modeling of the stroke as well? We could profile this part (and maybe optimize that part) but if I'm not...

Just to be thorough: if you save the file then reopen it, circles are still lines right ? Maybe `get_stroke_mut` sometimes fail to get the current brush stroke to push...

So I've done a first debug windows build here : https://github.com/Doublonmousse/rnote/actions/runs/15145490559 If you download the artefact, you get a zip containing a modified rnote exe (built on this branch https://github.com/Doublonmousse/rnote/actions/runs/15145490559)...

Yeah, so I'm wrong on both accounts then - the `insert_stroke` doesn't seem to take more time to process (in the microseconds there) - There is no apparent failure to...

I've done another debug build here https://github.com/Doublonmousse/rnote/actions/runs/15226437777 I've not yet looked at the dll issue though. Could you retry with the simple model for curves and show the results ?...

Ok so, I think the first stroke weirdness comes from ``` HISTORY: size of the history before filtering 3 and after 2 ``` rnote filters brushstroke event if they're too...

Also : fixes #1400

Is the second button seen as an eraser by any other app on windows? (journal, onenote, nebo, xournal). If so there's very little that can be done (because this means...