Skip to content
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

Clustering : Cluster Markers do not initially hide their items on the map #454

Open
timothy-moonware opened this issue Sep 5, 2023 · 1 comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@timothy-moonware
Copy link

When we first open the map and start the cluster algorithm, the clusters appear rendered with their assigned items still visible.
It is not until you zoom all the way in and back out do the clusters hide their associated items.

In GMUDefaultClusterRenderer::- (void)renderCluster:(id)cluster animated:(BOOL)animated
I recommend adding the following code at line 286 :

      for (id<GMUClusterItem> item in cluster.items) {
          GMSMarker *marker;
          if ([item class] == [GMSMarker class]) {
              marker = (GMSMarker<GMUClusterItem> *)item;
              marker.map = nil;
          }
      }

This causes the initial Cluster renders to hide their items from the map.

@timothy-moonware timothy-moonware added triage me I really want to be triaged. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Sep 5, 2023
@wangela
Copy link
Member

wangela commented Sep 5, 2023

If you would like to upvote the priority of this issue, please comment below or react on the original post above with 👍 so we can see what is popular when we triage.

@timothy-moonware Thank you for opening this issue. 🙏
Please check out these other resources that might help you get to a resolution in the meantime:

This is an automated message, feel free to ignore.

@iHackSubhodip iHackSubhodip added the priority: p2 Moderately-important priority. Fix may not be included in next release. label Nov 9, 2024
@wangela wangela removed the triage me I really want to be triaged. label Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

3 participants