crop_image_feature

[chaneylc]

Description

Photo traits can now define a crop region.

Workflow:
User must enable crop in trait definition, right now it is set to false as default. Like other trait parameters, this cannot be edited if data for that trait is already captured.

When observing data for that photo trait, the user can click the settings and define a crop region, or a dialog will show if the trait requires cropping and no region is defined when a photo is taken. In the latter case, the photo will be cropped and saved.

This feature introduced CropImageView which I added a fragment controller implementation along with an activity wrapper for the fragment. This is a modular and independent view, but requires two intent-based parameters, traitId (internal db id of the trait to update the crop region) and imageUri for the image to preview as it is cropped.

UI:
The CropImageView has a couple functionalities:

1. Users can drag the 4 boundary handles (top, bottom, start, end) within the bounds of the image to adjust ROI size
2. Users can drag the middle handle to move the entire region
3. Users can click save to save the rectangle coordinates to preferences for that trait
4. Users can click copy to save the rectangle coordinates to clipboard
5. Users can click reset to reset coordinates to the currently saved preferences
6. Users can click expand to reset coordinate to the image dimensions
7. Users can click/edit coordinate edit text, but coordinates will not be updated/invalidated unless the ACTION_DONE ime is pressed (the enter button)

Working with multiple devices:
User 1: set ROI, copy coordinate text and send to User 2
User 2: paste roi coordinates in edit text, press enter and save

• Needs testing on non-system cameras.
• Needs to disable crop setting button for traits that have it disabled.

Screen_recording_20250131_122857.mp4

Change Type

• ADDITION (non-breaking change that adds functionality)
• CHANGE (fix or feature that alters existing functionality)
• FIX (non-breaking change that resolves an issue)
• OTHER (use only for changes like tooling, build system, CI, docs, etc.)

Release Note

---

Release Type

For internal use - please leave these unchecked unless you are the one completing the merge.

• MAJOR
• MINOR
• WAIT (No immediate release, but the changelog will be still be updated if there is a release note.)