Repository navigation
Conversation
The eraser mode has it’s own keybind and line width, and uses the same drawing method as the drawing. The drawing code has been significantly reworked to share code between erasing, drawing and previewing changes for shapes.
This sounds like a fun idea.
This is not acceptable. A rework or rewrite should be a non-goal when adding features. 'Significant rework' is definitely out-of-scope here.
I appreciate your effort here but there are far too many changes to 'get it done' in this PR. I decided to try my hand at this to discover the subtleties and caveats. No AI or LLM was used and it took me about an hour. The block in the frame damage function could probably live in a separate function. Disclaimer: I am by no means a cairo expert. |
|
Thank you for your idea, it is implemented in #356. I was able to simplify the code even further than the patch above. I also added a Co-authored-by-you tag to the commit message. Please try the |
The eraser mode has it’s own keybind and line width, and uses the same drawing method as the drawing.
The drawing code has been significantly reworked to share code between erasing, drawing and previewing changes for shapes.
Disclosure : an LLM was quite extensively used for the cairo code, in part to get it done despite my inexperience with it. I have read and understand the code to the best of my abilities and take full responsability if something’s wrong.