Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 4.1
-
Fix Version/s: EE-4.1.0.RC1, EE-4.1.0.GA, EE-3.3.0.GA_P04, 4.2.BETA, 4.2
-
Component/s: ACE-Components
-
Labels:None
-
Environment:Any
-
Support Case References:Support Case #13607 - https://icesoft.my.salesforce.com/5007000001Tpwqe
Description
After the improvement added under ICE-10854, the customer reported that it's not possible to use ace:gMapInfoWindow in conjunction with ace:gMapMarker, when placing the marker via the new 'address' attribute. This is the case because the marker is not immediately initialized on the client; it's initialized only after receiving the results of a successful geocoding request, based on the specified address. So, when the info window initializes, it tries to find the corresponding marker instance, but this instance doesn't exist yet at that time.
The same situation occurs with ace:gMapEvent.
This can be solved by creating a registry of callback functions that the marker will consult once it's initialized after the geocoding request. If the marker finds callbacks for itself, it will execute them. These callbacks will safely initialize the info window and/or the event instances on the marker, now that it exists.
The same situation occurs with ace:gMapEvent.
This can be solved by creating a registry of callback functions that the marker will consult once it's initialized after the geocoding request. If the marker finds callbacks for itself, it will execute them. These callbacks will safely initialize the info window and/or the event instances on the marker, now that it exists.
Issue Links
- depends on
-
ICE-10854 ace:gMapMarker - Add ability to set marker with just an address
- Closed
r47075: added callback registry to initialize info windows and events on markers once the markers have been initialized in the client (4.0 trunk)