Latest Contributions by JeffBurgess

‎11-09-2017

I just stumbled across this post because I have the same question. The links that Shan sent refer to server codes as seen in the log, not codes as returned by the ArcGIS REST API when making HTTP requests. As seen in Flavie's example above, 500 is often returned when something's really wrong, like you used the wrong map service URL for a query or there's an internal server error. From memory, I seem to recall that you get a 498 error when a server is using the legacy "tokens" authentication method and the token is invalid. I've seen 499 errors too, but I don't recall what problem a 499 describes. Anecdotally, I have noticed that the error series follows HTTP error code series (4XX errors are a problem with the client's request, and 5XX errors are a problem on the server). But that doesn't really help when you're trying to understand the range of possible codes. A list of possible ArcGIS REST API codes (along with their meaning) would be quite helpful. -Jeff

‎10-25-2012

Is there a way to standardize the text input block size for the attribute inspector? I notice that it is dependent on the size of the field but I cannot find anywhere in the skin where the code decides how big to make the input text box. I have a lot of fields and think it would be more friendly if all input text boxes were of the same size. Thanks for any help! I realize this is an ancient post but I came up against a similar problem and figured it wouldn't hurt to post my solution here. If you run out of options trying to skin the attribute inspector, you can always go with the nuclear option and extend that class itself. If you override the createFormItemComponent method you get a lot of control over the UIComponent instances that the AttributeInspector makes. In my case, I needed to change the max height and width of the TextArea controls. Here's what I ended up doing, roughly: public class CustomAttributeInspector extends AttributeInspector { public function CustomAttributeInspector(featureLayers:Array=null) { super(featureLayers); } override protected function createFormItemComponent(featureLayer:FeatureLayer, field:Field, fieldInspector:FieldInspector, fieldValue:Object):UIComponent { var uiComponent:UIComponent = super.createFormItemComponent(featureLayer, field, fieldInspector, fieldValue); if (uiComponent is TextArea) { // Darn those TextAreas. Make 'em narrower! uiComponent.maxHeight = 80; } // We want all components to be 100% of the parent's width uiComponent.percentWidth = 100; return uiComponent; } }

‎01-26-2011

CORRECTION: I am using the 2.2 version of the Viewer for Flex.

‎01-24-2011

My question has to do with the current (v2.3) implementation of WidgetManager. Here's my scenario: I'm building a widget that needs to load up a custom info template. In my widget, I'm dispatching a DATA_CREATE_INFOWIDGET event much like the stock Locator widget does. Like in the Locator widget, I am including a callback function with that event. Problem: when that info widget has finished loading, the wrong callback function is invoked! Instead of calling the callback function from my custom widget, it is calling the callback function in the Locator widget. NOTE: the Locator widget and my custom widget are both set to preload=true. I did a little snooping and discovered that the WidgetManager stores the callback function in a private variable (m_infoWidgetCallback). Because of the order of configuration, the WidgetManager ends up overwriting my custom widget's callback function reference in m_infoWidgetCallback before it even has a chance to call it for my custom widget. So when the infoTemplate for my custom widget finally loads, WidgetManager actually erroneously invokes the Locator widget callback. It seems that the WidgetManager singleton needs a more sophisticated method for storing and executing infoTemplate callback functions. In general practice I would recommend never storing transient data like this in a singleton property or private variable as it is sure to produce lots of hard to find timing-related bugs under load. I am trying to avoid modifying the core viewer as much as possible but this seems like a case where I may be forced to. Am I missing something? EDIT: After looking a little further into the issue, I noticed some interesting constants in the AppEvent class: INFOWIDGET_REQUEST and INFOWIDGET_READY. However they are not currently used. Perhaps they will be used in the future to refactor away from the "request event + callback" approach to a "request event + response listener" approach? This would be safer and would keep the WidgetManager code simple.

‎10-29-2010

FYI, I worked through the NAnt build issue. Here's the block that does the work: <target name="compileMap">  <property name="flexsdk.dir" value="${environment::get-variable('FLEX_SDK_41_HOME')}"/> <exec basedir="${flexsdk.dir}/bin/" program="mxmlc.exe" failonerror="true"> <arg line="-target-player 10.0.0.0"/> <arg line="-library-path "${flexsdk.dir}/frameworks/libs""/> <arg line="-library-path "${flexsdk.dir}/frameworks/libs/player/10.1""/> <arg line="-library-path "${flexsdk.dir}/frameworks/locale/en_US""/> <arg line="-library-path ./myproject/libs/"/> <arg line="-source-path ./myproject/locale/{locale}"/> <arg line="-output ${map.compilerOutputDir}/bin/index.swf"/> <arg line="./myproject/src/index.mxml"/> </exec> </target>

‎10-29-2010

I'm having the same compilation issues when trying to compile from CruseControl.NET / NAnt. First I was getting embedded asset compilation errors. Adding a leading slash to the asset path fixed those (I think). Did you ever resolve your resource bundle compilation problem?

Online Status	Offline
Date Last Visited	‎11-11-2020 02:23 AM

My Ideas

Latest Contributions by JeffBurgess

Re: ArcGIS Server REST API, error codes documentation?

Re: Attribute Inspector Limitations

Re: WidgetManager calls incorrect callback when loading multiple infoWidgets

WidgetManager calls incorrect callback when loading multiple infoWidgets

Re: Unable to resolve resource bundle - 47 errors

Re: Unable to resolve resource bundle - 47 errors

Re: ArcGIS Server REST API, error codes documentat...