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
In the v3 Lime app version, the Locate screen is now merged with the Mesh Map screen as part of the new shared state API. This relies on shared state information to display nodes on the map. However, there are some issues:
Node Location Updates: When using the old API to set a node’s location, the map does not update until the shared state reflects the new location. This can cause delays and inconsistencies.
Link Location Updates: The shared state does not update link locations instantly, which may lead to confusion for users.
Proposed solution
Update the shared state logic to ensure that inserting a node location automatically updates the Lime node configuration. This would:
Enable location changes to be managed entirely through the shared state API.
Ensure all related updates (e.g., node and link locations) are performed seamlessly and instantly within the shared state.
The text was updated successfully, but these errors were encountered:
Problem Description
In the v3 Lime app version, the Locate screen is now merged with the Mesh Map screen as part of the new shared state API. This relies on shared state information to display nodes on the map. However, there are some issues:
Node Location Updates: When using the old API to set a node’s location, the map does not update until the shared state reflects the new location. This can cause delays and inconsistencies.
Link Location Updates: The shared state does not update link locations instantly, which may lead to confusion for users.
Proposed solution
Update the shared state logic to ensure that inserting a node location automatically updates the Lime node configuration. This would:
The text was updated successfully, but these errors were encountered: