Repository navigation
Draw unclean AR spots as outlines and face the closest spot in the result model #146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
b8b3c37
ios: result marks follow-ups from #110 (heading, AR outline, outline …
AidenJohnston 0964ecc
ios: the result card offers no capture once the camera has failed
AidenJohnston 6e8403f
Merge origin/beta into t3/110-result-details-followups
AidenJohnston 9a0e275
fix(ios): aim the AR spot checks at the outline for an unclean spot
AidenJohnston File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For an unclean spot, this branch moves the only spot mark to the ground, but
ScanEngine.showResultInCameraandSpotDirectionstill testspotCenter(on:)at half the battery height. When that midpoint is inside the viewport while the ground footprint is below it,resultIsDrawn()suppresses the Canvas fallback and the chevron remains hidden, leaving the user with no visible indication of the spot. Use the footprint's ground-level center for the visibility and direction targets when rendering an outline.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@AidenJohnston Independent nine-file review and lead source tracing confirm this at 6e8403f. Both renderers now put an unclean spot outline near ground level, while ResultARScreen.spotCenter:88-91 and ScanEngine:1488 retain half-battery-height focus. With that midpoint inside the clear band and the footprint below the screen or controls, neither the mark nor a downward chevron is visible. This affects Canvas on non-LiDAR too; restoring Canvas alone is insufficient. Please make the shared visibility/direction target follow the rendered mark, retaining midpoint targeting for clean batteries, and cover both projections. The clean resultAR demo does not exercise this case. Source verified only; no physical reproduction here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 9a0e275.
ResultMarkLayout.focusHeight(mark:batteryHeight:)(HouseScanKit) gives the height the AR view aims at: the battery middle for a clean spot, the ground for an outline.ResultPresentation.spotCenter(on:)now uses it withspotMark(spotIsClean:), so both the edge chevron (SpotDirection, Canvas and RealityKit paths alike) andScanEngine.showResultInCamera's focus forresultIsDrawn()follow the rendered mark. Clean batteries keep the midpoint.ResultMarkLayoutTests.focusHeightFollowsTheMarkcovers the helper.