Latest Contributions by IsaiahAguilera

James, I would say your best bet would be to use two separate config.xml files. You could have the default application load with the public services that everyone could see and then have some sort of login system to get to the secured services from the public application.  A simple hyperlink in your header controller that uses the custom URL functionality built into the viewer could work. So your hyperlink could say Login and the URL would be your app's URL plus the specific config file for the secured version. Example http://yoursite.com/index.html?config=configSecure.xml If your services are secure the new config will reload the site and will prompt the user for credentials.  This could save time because you would only have a separate config xml instead of a separate application.  That is just my opinion. Hope this helps, ... View more

Yes the skins are included when you download the API.  You can modify them and then reference them accordingly in your application. ... View more

Sure, MVC stands for Model-View-Controller it's a coding practice used by many different languages. There are different frameworks you can use to accomplish this. If you would like to just use the model portion you could avoid the framework part although it would be beneficial for you to try the whole concept. For the model portion you would create an action script class file named model.as then you could create a singlton instance of it which would hold all the variables you wanted to use globally. You could then reference or bind to them anywhere in your app. If you learn controllers it's like the model but instead of variables it holds the functions. It's definitely something that can take your coding to the next level. The best examples and framework for flex I have found is here. http://thunderheadxpler.blogspot.com/2011/10/micro-architecture-for-flex-ria-and-rma.html Mansour Raad explains it very well. Check it out. ... View more

Glad to help. Don't forget to mark my post as the answer if you feel this solves your problem. Thanks. ... View more

Clinton, You might consider passing the array directly from the pushView function.  So instead of navigator.pushView(EditorView2, event.featureSet) you could use navigator.pushView(EditorView2, event.featureSet.attributes) Another solution albeit a more involved one would be to use a sort of MVC solution and declare an array in a model which you could then reference directly from multiple views. So on your execute complete of the query you could set the public array in your model equal to your event attributes. This way might require more explaining if interested but could save some headaches in the long run. ... View more

Yeah that's what I was afraid of.  I was hoping to keep it simple just using the infowindowrenderers and not have to worry about adding a graphic on click.  Thanks Robert. ... View more

That was it. I used "default" instead of "defaults". Renaming it and running a clean made it all work.  Thanks for all of your help with this.  It is very appreciated. ... View more

Thanks for spending so much time on this Dasa! I made the specified changes and I was still getting an error.  So I did some digging and found that I had to also change the AttributeTableSkin and the RelationshipInspectorAttributeInspectorSkin.  I was still getting an error so I just went looking for the calendar field in any file and it was in those two also.  <fx:Component id="dateField">         <!--<fieldClasses:CalendarField/> -->    <fieldClasses:TextField minWidth="200"/>         </fx:Component> I wasn't sure how to reference the RelationshipInspectorAttributeInspectorSkin in the default.css so I just made a com.esri.ags.skins package and put them all in there to bypass the css and it got rid of my runtime errors.  Did I do something wrong that I had to change those two files as well? I am not using those components at all I am just running the basic map still. <ns:Map id="map">   </ns:Map> Anyways I am able to use everything either way now. I was just curious about the other two skins ans why I had to change those also. Thanks, ... View more

The other option mentioned at the bottom of that link is to remove references to the RelationshipInspector in the PopUpRendererSkin. The RelationshipInspector uses the AttributeInspector which by default, uses mx components like DateField. This has been an issue since 3.1, but now with 3.4, you're getting the error right away. Ive changed everything I can think of in the PopUpRendererSkin and I cannot get the runtime error to go away. I know I am probably missing something or not even doing it the right way but I can't get it working.  I would hate to switch to the older api but that might be my only option for now.  Any help would be appreciated. ... View more

Thanks Dasa! I understand now.  To do this, do I just grab a copy of the skin from the api download and then comment out any thing in the PopUpRendererSkin.mxml that references the RelationshipInspector?  I think I am missing something because I am still getting the error.  Is there more involved then what I am doing? Thanks, ... View more

You'll need to add a reference to the mx.swc. See: https://developers.arcgis.com/en/flex/guide/mobile-flex.htm Thanks for you help Dasa! I was wondering if I needed to do that but I have not needed to do this with the 3.3 API and I am not using any MX components either.  Is the new 3.4 API dependent on the mx.swc? Also when I do add the mx.swc and the sparkskins.swc like you suggested, simply adding a map component again gives me 5 warnings as shown in the picture.  Is there any way to remove these warnings?  Again this is a blank project with just a map component added so far. [ATTACH=CONFIG]26323[/ATTACH] Thanks for your help! ... View more