The View Region
None of the eight applications that draw findings publishes an image of its own — each reads one from
another application — so Cockpit follows the module’s input-image-address to find the picture the
findings belong on. If that has not been set, the view reports so rather than showing an empty frame;
point the module at a camera’s image node first.
The view is the region that was searched
Where a module searches only part of the image, you see that part, at its own size, with the findings on it — which is exactly what the detector was given. A module with no crop configured searches the whole image, so its view is the whole frame.
This applies to the four applications with modules. A code reader reports nothing but the codes it found, so its view is always the whole picture it read.
The region comes from the result itself, not from the module’s crop settings, so editing the crop after a run does not move the picture out from under the findings still on display. The view keeps showing what that result came from until the next run replaces it.
When the image size no longer matches
If the last result was found in a camera image of a different size than the one now displayed, the findings are not drawn and a note says which size the result belongs to. What to do is described in Troubleshooting: Findings are not drawn.