Clip and Erase area tools ignore protected state of symbols

[dl3sdo]

While the Clip and Erase area tools only operate on the current map part and thus all objects on other map parts are automatically protected, objects on the current map part with symbols being protected are affected by both tools however.

This is not (yet) a proposal to change the current behaviour.
Advantage:

• If the user has protected a lot of symbols in order to not select them unintentionally while editing, it's easy to erase an area of the map without having first to unprotect all symbols, doing the erasure and then protecting those symbols again

Disadvantages:

• It might be unexpected (and maybe even unnoticed, e.g., for objects with protected and hidden symbols)
• It requires objects to be excluded from erasing to be moved to another map part

BTW: the behaviour can be easily changed,
in function void CutoutTool::apply(Map* map, PathObject* cutout_object, bool cut_away) the line
map->getCurrentPart()->applyOnAllObjects(std::ref(operation));
needs to be replaced by
map->getCurrentPart()->applyOnMatchingObjects(std::ref(operation), [](const Object* object) { return !object->getSymbol()->isProtected(); });

How is the experience with the current behaviour?

[krticka]

I was thinking what is my current workflow and expectations. In 95% I am using clip to clip map to some shape for the competition, not aware about symbol status. So I expect that within this tool everything is clipped regardless symbol status.

[jjojala]

How about, if the Mapper would ask from the user in such a situation (clipping would consern protected or hidden symbols) what to do? That way the user would decide how to continue upon her/his needs at that particular case. Generally agree with @krticka (that's my usual use case too).