IssueTracker

I guess hidden should just be defined. Meaning, right now, hidden should just defined as "whether this fragment was hidden as part of a transaction".  Hidden is not equivalent with visibility. I think that's where the confusion comes from.

We have passed this to the development team and will update this issue with more information as it becomes available.

Yeah, I'm seeing this issue as well, currently this is the workaround that I've come up with:

    // This method is called when hide()/show() methods are called on the transaction. Unfortunately Android doesn't
    // propagate it to the child fragments (even though their visibility is affected by the parent visibility), so we
    // do it manually.
    override fun onHiddenChanged(hidden: Boolean) {
        super.onHiddenChanged(hidden)
        childFragmentManager.fragments.forEach { it.onHiddenChanged(hidden) }
    }

@4 That actually won't technically fix as isHidden() will technically mismatch with the state passed into the child fragment.  Each child fragment legitimately needs to have their state set to hidden.

@6 I don't know what the ramifications are, but when you iterate, you can save the "currentState" and then hide them all via a transaction. When restoring to visible, restore to the original state.

Project: platform/frameworks/support
Branch: androidx-main

commit 02290cddca3d5e4dc94e2c5f77a6728ad970b204
Author: Jeremy Woods <jbwoods@google.com>
Date:   Thu Oct 07 13:11:45 2021

    Dispatch onHiddenChanged to child fragments
   
    When a parent fragment is hidden all of its children will automatically
    be hidden, but we never call onHiddenChanged on any of the children.
   
    We should dispatch onHiddenChanged down parent's entire hierarchy and
    ensure that `isHidden()` also considers the parent's state.
   
    RelNote: "Parent fragments will now dispatch `onHiddenChanged()` down
    their entire hierarchy before launching their own call back."
    Test: added test
    Bug: 77504618
   
    Change-Id: Iedc201ab435cb963e81bc02d203d4d37ff827e01

M       fragment/fragment/src/androidTest/java/androidx/fragment/app/FragmentViewTest.kt
M       fragment/fragment/src/main/java/androidx/fragment/app/FragmentStateManager.java
M       fragment/fragment/src/main/java/androidx/fragment/app/FragmentManager.java
M       fragment/fragment/src/main/java/androidx/fragment/app/Fragment.java

https://android-review.googlesource.com/1850016

Thor/Pamela, now that this has been acknowledged for v3 do you have any suggested API features we should look for in the interim.  I note that there is no addoverlay event on the Map class in v3, although there is a click event for KmlLayer (but that's only useful for managing click events rather than exposing the overlays).

It should also be noted that this now affects the KmlLayer class rather than the former GGeoXml.

Given that v3 renders *all* KML features except GroundOverlays as server side tiles rather than streaming them to the browser for client side rendering, does this FR still apply?

Given that v3 renders *all* KML features except GroundOverlays as server side tiles rather than streaming them to the browser for client side rendering, does this FR still apply?

The point of the exposure for me is that I'd like to place a KmlLayer on the Map and render a list of the overlays next to the map which can be clicked on to trigger the markers.  Almost like the support available via entering the address of a KML file into the search box on maps.google

s there any way to extract the polygons after loading a kmlLayer?

I would suggest that this FR is absolutely necessary, for the reason given by @sparks.phill.

While I would agree that much of this feature request no longer applies due to the v3 implementation techniques, it would be nice to be able to trigger a click event on a feature give either its coordinates or its placemark id.

Hi.

I want to add tens of thousands of points on the map (with the help of elements <link>) in "inactive" and then using Javascript to switch the selected items (taken with the object ID) to "active". Without the provision of a list of objects in the KML file, I do not see a way to achieve this.

So: getObjectById ("objectId") and then updateStyleUrl("#active")

Best Regards

We have a current application that uses GoogleMaps v2 API to place markers and let the user toggle them on and off via HTML controls and javascript.

We want to rewrite our application in v3 and change it to import KML containing PlaceMarkers instead of creating the markers in script (that way our customers will have a data file that they can use outside their public web page).  We can not make that migration until this feature is added.

This FR is absolutely necessary

This was a v2 feature request and doesn't make sense in the context of v3.

Plase! I need to call placemark in my KML file with a javascript link into .html! any way to do that?


tks.

Still waiting 12 years after 'wontfix'...