topic Re: Info Windows for Feature Layer - odd behavior in ArcGIS API for Flex Questions

Info Windows for Feature Layer - odd behavior

CarmenDurham — Tue, 10 Mar 2015 21:16:32 GMT

Hello all,

I am using the following sample code in my application - but stripped down to just using the feature layer and the InfowindowRenderer.

InfoWindows for FeatureLayer—ArcGIS API for Flex | ArcGIS for Developers

Our app displays Field Interview (where they talk to people on the street acting suspiciously) information that the Police have entered into their application (Cityworks). The infowindow works fine where there is a single point. The issue is where multiple points exist.

At first, they display fine like below. I can toggle through the different features at this location without problem.

But then after an action happens (detailed below), if one clicks on the navigation arrows to toggle through other features (2 of 5, 3 of 5, etc), the popup will switch to this - looks like some default window and default black symbol (none of this is in my code).

What actions made this happen?

It depends on the type of map service/feature layer is used - I tried two:

1) Scenario 1 - table (from Cityworks) loaded in ArcMap and displayed as x-y event theme. The x-y event theme published in a map service. No object ID. The above weird Infowindow appears after you have displayed the infowindow (correctly) but then pan/zoom while it is open and then click on the arrows to cycle through the features on the popup.

2)Scenario2 - I thought the #1 might xy event theme be the problem so I exported to a static feature class and published a map service. I thought the problem was solved because I could open an infowindow where multiple features were located, pan/zoom around, but still cycle through the features on the popup without a problem.

BUT NO --- in flex, I have a "timer set to refresh service" at an interval -- once the refresh happened in flex on scenario #2, I clicked an arrow on an already opened infowindow and the weird infowindow displays.

Anyone know what can be done about this odd infowindow appearing?

4.6 SDK 3.0 API

Thanks,

Carmen

Re: Info Windows for Feature Layer - odd behavior

RobertScheitlin__GISP — Wed, 11 Mar 2015 05:02:28 GMT

Carmen,

The first thing I would try is to use the latest API.

Re: Info Windows for Feature Layer - odd behavior

CarmenDurham — Wed, 11 Mar 2015 15:47:53 GMT

I reverted back to trying the sample as-is with api 3.7 (downloaded this a.m.) and SDK 4.6.

Sample works fine as is with above. But...

When I add the "refreshinterval" to the feature layer (below)

the issue happens.

Run the application and click on an area that causes multiple features to display in the infowindow and leave the infowindow open like so.....

Then, as soon as you see the refresh occur for the layer, click on the arrow to view the other features. Immediately, the infowindow will change to:

Luckily, you can close the window and click on the features again and return to the expected infowindow, but it is kind of a pain. I thought maybe the user won't ever notice it, but they found this quickly.

If it is a bug that will likely never get fixed, just let me know and we will live with it until the apps are converted to javascript (but that could be a while). But if someone knows a fix, please let me know!

Thanks,

Carmen

Re: Info Windows for Feature Layer - odd behavior

RobertScheitlin__GISP — Mon, 16 Mar 2015 16:59:28 GMT

Carmen,

It appears that the infoWindowRenderer is being lost/reset to the default infoWindowRenderer on refresh. I would call tech support and give them your simple sample case about and see if there is anything they can do for you. I have spent a hour trying myself to reset the infoWindowRenderer to the one specified in the MXML code but have been unsuccessful.

Re: Info Windows for Feature Layer - odd behavior

CarmenDurham — Mon, 16 Mar 2015 18:36:07 GMT

Thank you, Robert, for taking so much time to see if there was a workaround.

I will submit to technical support as a bug and post any conclusions to here.

Thanks,

Carmen