You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great if adding an overview map were simpler. One way of doing that would be to have a custom view modifier for the overview map in the toolkit:
As a proof of concept, it isn't without problems. We would need to change how those modifiers on map/scene view are implemented since users may also want to use them themselves (currently each subsequent use would override the previous).
The overview map could be customized with an overviewMapStyle(_:) modifiers, similar to other SwiftUI views. This should be explored as part of this issue; the OverviewMap already provides modifiers for symbol, map, and scaleFactor. Should they be combined into one overviewMapStyle(map:, symbol:, scaleFactor:)?
To get around the .onViewpointChanged(kind:)/.onVisibleAreaChanged() issue, maybe the .overviewMap(alignment:) modifier could take an optional binding to a Viewpoint and visible area Polygon and then update it alongside the local viewpoint and visible area.
It would be great if adding an overview map were simpler. One way of doing that would be to have a custom view modifier for the overview map in the toolkit:
A proof of concept is as follows:
As a proof of concept, it isn't without problems. We would need to change how those modifiers on map/scene view are implemented since users may also want to use them themselves (currently each subsequent use would override the previous).
The overview map could be customized with an overviewMapStyle(_:) modifiers, similar to other SwiftUI views. This should be explored as part of this issue; the
OverviewMap
already provides modifiers forsymbol
,map
, andscaleFactor
. Should they be combined into oneoverviewMapStyle(map:, symbol:, scaleFactor:)
?To get around the .onViewpointChanged(kind:)/.onVisibleAreaChanged() issue, maybe the .overviewMap(alignment:) modifier could take an optional binding to a Viewpoint and visible area Polygon and then update it alongside the local viewpoint and visible area.
Thanks to @philium for the suggestion!
The text was updated successfully, but these errors were encountered: