When localPosition was first added to the search result,
it was defined as relative to the layer that owned the annotation,
which turned out to be a design mistake.
The offset from the layer is meaningless and unreliable.
For example, a Transform widget draws on the same layer
with an offset if the transform matrix is a simple translation,
or push a dedicated TransformLayer if the matrix is non-trivial.
The former case keeps the previous coordinate origin
(for example, the top left corner of the app),
while the latter case moves the position origin since
it’s on a new layer. The two cases might not produce noticeable
visual differences, since the extra layer might just be a scale of
99%, despite that the annotation search returns different results.
In order to make this local position reliable, we have to choose
one of the results to stick to.

Description of change

The localPosition returned by an AnnotatedRegionLayer
is now the local position it received subtracted by offset,
where offset is the location of the clipping area relative
to the layer.