https://bugs.kde.org/show_bug.cgi?id=492434
Dmitry Kazakov <dimul...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|CONFIRMED |RESOLVED
Latest Commit| |https://invent.kde.org/grap
| |hics/krita/-/commit/4009f8f
| |911f6ec9006c4652eb029d3213d
| |f76a06
--- Comment #4 from Dmitry Kazakov <dimul...@gmail.com> ---
Git commit 4009f8f911f6ec9006c4652eb029d3213df76a06 by Dmitry Kazakov.
Committed on 15/11/2024 at 14:00.
Pushed by dkazakov into branch 'krita/5.2'.
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/4009f8f911f6ec9006c4652eb029d3213df76a06
--
You are receiving this mail because:
You are watching all bug changes.
