Add FloatingPanelDetent.Preference

[dfeinzimer]

In certain situations, a view presented in a floating panel needs the map view to be revealed for user interaction:

Typically, this would require the presented view to have a binding to the floating panel's detent; however, the view might not be presented in a floating panel. By providing this internal preference, Toolkit components can communicate a preferred detent to the Floating Panel without developers needing to write any code. Example usage.

---

• Testing
• Can UtilityNetworkTrace.floatingPanelDetent(_:) be deprecated?
• Should this be a public type?
• Does this take too much control away from the developer?

[mhdostal]

this looks good and is a nice way to override the detentions when a component needs to.

[dfeinzimer]

A reservation I have with this approach is that supporting the same behavior for sheets seems problematic. Sheets (surprisingly) don't animate nicely when nested views with the presentationDetents(_:) modifier applied appear and disappear:

Should we forego this magic approach and instead have developers manage their detents by adding more cases to FeatureFormView.EditingEvent like mapInteractionStarted/mapInteractionEnded?

[mhdostal]

Should we forego this magic approach and instead have developers manage their detents by adding more cases to FeatureFormView.EditingEvent like mapInteractionStarted/mapInteractionEnded?

Will this alleviate the problems with sheets?

[dfeinzimer]

Will this alleviate the problems with sheets?

It doesn't seem to. There's some discussion about this issue here, but I haven't yet been able to make the suggestions work correctly with our views.

Regardless, it might be best overall to take the sheet/panel agnostic approach and just report what the user is doing via the new cases suggested above on FeatureFormView.EditingEvent or another new enum altogether.

[mhdostal]

Regardless, it might be best overall to take the sheet/panel agnostic approach and just report what the user is doing via the new cases suggested above on FeatureFormView.EditingEvent or another new enum altogether.

Ok. Let's try and make it the default/predominant use case work with little or not extra code.