Solved! Go to Solution.
Thanks Bjorn, I am glad ESRI is looking into fixing this issue in the 10.2 release but you guys need to realize that most agencies are a year or more away from upgrading to 10.2. We really need a patch to be created for 10.0 and 10.1 users, which is 99% of current ESRI users right now.
So, once you create the fix for the new version could you also create a patch that we can add into 10.0 and 10.1? This is more important to us than creating a fix for a new release that we will not use for at least another year.
Thanks,
Mike
Thanks Bjorn, I am glad ESRI is looking into fixing this issue in the 10.2 release but you guys need to realize that most agencies are a year or more away from upgrading to 10.2. We really need a patch to be created for 10.0 and 10.1 users, which is 99% of current ESRI users right now.
So, once you create the fix for the new version could you also create a patch that we can add into 10.0 and 10.1? This is more important to us than creating a fix for a new release that we will not use for at least another year.
Thanks,
Mike
I think he's referring to the next Flexviewer/Flex API release (v3.5), not ArcGIS 10.2.
It seems to work fine for certain cases but not all. I've created https://github.com/Esri/arcgis-viewer-flex/issues/157 as a bug to be fixed for next release.