https://bugs.kde.org/show_bug.cgi?id=492434
Dmitry Kazakov <dimul...@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/-/commit/4009f8f |hics/krita/-/commit/f639df1 |911f6ec9006c4652eb029d3213d |7feea76ff67985e96e4b6c517b9 |f76a06 |69fb1a --- Comment #5 from Dmitry Kazakov <dimul...@gmail.com> --- Git commit f639df17feea76ff67985e96e4b6c517b969fb1a by Dmitry Kazakov. Committed on 15/11/2024 at 14:07. Pushed by dkazakov into branch 'master'. Make sure that point-based snap points have higher priority than line-based ones Basically, if grid intersection lays near (or on the top of) the guide (or image bounds), then this intersection should have higher priority than snapping to a "mere" line. Ideally, we should make some clver resolver that can also find intersections between the different snap strategies, e.g. inteersection between a guide and a grid line. But it needs quite a lot of redesing in our snapping code, so we can postpone it now. M +1 -1 libs/basicflakes/tools/KoCreatePathTool_p.h M +9 -5 libs/flake/KoSnapGuide.cpp M +33 -16 libs/flake/KoSnapStrategy.cpp M +15 -2 libs/flake/KoSnapStrategy.h M +1 -1 libs/ui/canvas/KisSnapPixelStrategy.cpp M +1 -1 libs/ui/canvas/KisSnapPointStrategy.cpp M +4 -1 libs/ui/canvas/kis_snap_line_strategy.cpp https://invent.kde.org/graphics/krita/-/commit/f639df17feea76ff67985e96e4b6c517b969fb1a -- You are receiving this mail because: You are watching all bug changes.