Snapping to objects on different map parts

[dl3sdo]

Mapper currently shows a behavior which is in contradiction to how map parts are handled otherwise:
Snapping to the closest object (and also following a path) is not limited to the current map part.

Maybe this is the intended behavior as the code uses the function Map::findAllObjectsAt() which iterates over all objects on all map parts and which is not used somewhere else.
There is another function Map::findObjectsAt() which just iterates over all objects on the current map part, so fixing that behavior is straightforward.

What is the desired behavior?
Personally, I'm in favor of limiting snapping to the current map part.

[krticka]

When I have my colleague's map as different map part and I want to join precisely my part during mapping, snapping can be beneficial. I don't think there is a clear answer as to whether this behavior is desirable or not.

[lpechacek]

The question might be difficult to answer without knowing the idea behind map parts. Maybe snapping was intended, maybe it was not. The commit message does not help to solve the puzzle and I'm unable to find a mailing/list discussion that would clarify the intent either. Maybe the patch author or committer will recall the details.

I'm using map parts as an object-level protection. There is symbol-level protection - protected symbols - and I can still snap to the objects protected that way. Then there is object level protection - objects are in a different part - and I can snap to them. Last but not least, there are templates - which is absolute protection - and I cannot even snap to the objects (but it might be nice if I could :) ). My use case is the same as for @krticka . I want to precisely align my map part to colleague's one. HTH

Edit: After some clicking around, I've found the merge request that introduced map parts: https://sourceforge.net/p/oorienteering/code/merge-requests/3/