Lefteris, That is the problem... The LayerEvent.UPDATE_START and LayerEvent.UPDATE_END that are attached to the feature layer, are added by the AttributeTable Flex API component, and thus they are not exposed to you as a developer. The LayerEvent.UPDATE_START and LayerEvent.UPDATE_END both call CommitProperties function inside the component. The only reason I know this is by using a customized version of FlexSpy to see the eventListeners that are added by the AttributeTable component. The only possibility I can think of is to extend the AttributeTable component and override the CommitProperties function, but I don't know what all the function is doing.
Lefteris, I have to take back my suggestion as when I did my test app it was not using the AttributeTable widget, but just a Flex API app that was using an AttributeTable component, and I did have a Monkey Patch applied that gives me the removeEventListeners (which normally would not be there). I have now tried to duplicate my success in the test API app, but this time using viewer and the widget, and I have been unsuccessful. Oh, well I thought I had an easier route for you, but I didn't.
Lefteris, Strange in my test application it did exactly what you asked for, prevented the zoom or pan from updating the table.
Lefteris, This might have some unforeseen consequences but try thisThe yourFeatureLayer is the id of your feature layersyourFeatureLayer.removeEventListeners(LayerEvent.UPDATE_END); yourFeatureLayer.removeEventListeners(LayerEvent.UPDATE_START);
yourFeatureLayer.removeEventListeners(LayerEvent.UPDATE_END); yourFeatureLayer.removeEventListeners(LayerEvent.UPDATE_START);
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.