This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Krita snapping Broken?

Tags: None
(comma "," separated)
bobob
Registered Member
Posts
6
Karma
0

Krita snapping Broken?

Tue Dec 11, 2018 6:56 pm
Using krita 4.1.5
When using the move tool, snapping does not seem to work.
View/snap to/*
ahabgreybeard
Registered Member
Posts
1269
Karma
11
OS

Re: Krita snapping Broken?

Tue Dec 11, 2018 9:07 pm
Using the krita 4.1.5 appimage, I've just had the Move tool snapping to the grid and to guides while moving a selected painted area. What did you do that makes you think that it doesn't work?

ADDED: I've just noticed that though the Move tool does snap to the grid, the snapping is not to the drawn grid but to an offset from the drawn grid. I think this is related to how krita makes an 'extent of content' box around image content. This is also the case when you make a selection (the selection box snaps to the grid) but when you move the selection, the snapping is to an offset from the grid. With this selected area case, krita draws some kind of 'content' box that is not the same as the selection you drew and which seems to snap to an offset from the grid. Is this what you mean?
bobob
Registered Member
Posts
6
Karma
0

Re: Krita snapping Broken?

Thu Dec 13, 2018 4:46 pm
Thanks for taking the time to anserr. For me snapping to grid works. But none of the other snapping do anything. Most of the time people need to snap to document bounds, other layers or placed guide rulers, for me it is impossible to snap to any of these regardless of how I tinker with it. Only snapping to grid seems to work.
User avatar
rbreu
Registered Member
Posts
52
Karma
0

Re: Krita snapping Broken?

Thu Dec 13, 2018 7:21 pm
You might be running into this bug.
ahabgreybeard
Registered Member
Posts
1269
Karma
11
OS

Re: Krita snapping Broken?

Thu Dec 13, 2018 8:07 pm
With the 4.1.5 appimage, I've just done snapping to Guides, Centre and Image Bounds. It's the Move cursor that snaps, not any selection or content bounding box so it depends where the cursor is when you click the mouse. This is the cause of the 'offset' that I mentioned in my previous reply. This is a known thing, apparently.


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], Sogou [Bot], Yahoo [Bot]