Erasing faster skips some strokes

[mahdihasan2006]

Description
Erasing faster skips some strokes.

To Reproduce
Steps to reproduce the behavior:

1. Open Rnote
2. Draw some lines or anything
3. Run the eraser over the lines slowly and then quickly
4. You will see different results

Expected behavior
Eraser should erase all the lines it crosses.

Console Output

2024-10-04T08:29:30.801574Z DEBUG rnote: .. tracing subscriber initialized.

(rnote:2): Gtk-CRITICAL **: 14:29:43.443: The layout manager of type GtkBoxLayout 0x558474123790 does not create GtkLayoutChild instances

Video

Screencast.from.2024-10-04.14-14-01.mp4

Desktop (please complete the following information):

• OS: Fedora 40
• App Version: Rnote v0.11.0
• Installation Source: Flatpak
• Desktop Environment: Gnome 46.5
• Display Server: Wayland
• Input Source: External Graphics Tablet

[Doublonmousse]

If I'm not mistaken, the eraser works per event. Hence if you move fast, you may not have a (x,y) coordinate close to every line.

The fix would be to store the previous coordinate (x_0,y_0) and when a new event (x,y) happens, erase the polygon corresponding to the space that the eraser got through between the two events (Minkowski sum between the line between the two events and the eraser square)

[mahdihasan2006]

Whatever it is. It's annoying when I try to do things quickly.

[Doublonmousse]

I've started to look at where/how I want to do this. Ideally, I'd want #1235 to land first though before starting this part.

It must be one of the most widespread bug for this kind of application (present in xournalpp, lorien, saber, journal ..)

It's made worse by this line

rnote/crates/rnote-engine/src/pens/penholder.rs

Line 497 in 7f3ff8a

PenStyle::Eraser => BacklogPolicy::Limit(Duration::from_millis(33)),

That limits the event rate of the eraser to the display refresh rate (so if you have 3 events over a frame, only the last one is sent)