Latest Contributions by JoshWhite

Similar idea that has more votes at https://c.na1.visual.force.com/apex/ideaView?id=0873000000087R4AAI probably should be merged. ... View more

I agree with mping ... View more

I'm having troubles understanding why people are voting this down, I would very much like this feature.  It is difficult to exchange GIS files over email and this would help.  I often end up zipping when the shapefile doesn't work.  ... View more

I'm having troubles understanding why people are voting this down, I would very much like this feature.  It is difficult to exchange GIS files over email and this would help.  I often end up zipping when the shapefile doesn't work.  ... View more

I still say that part of the problem is how you upgrade to a new version.  Copying xml could cause all sorts of problems.  There needs to be some sort of script or other program that automatically updates your xml files to the new version.  If something can't be updated for whatever reason, it could be tagged in the xml or a txt file could be created.  If I knew anything about scripting I would work on something like this but I don't so I will have to rely on somebody else to do it. ... View more

You just need to publish a map service with your imagery in it. Your config file would need something similar to that below: <layer label="Aerial"  type="dynamic" visible="true"                    url="http://gis-server/ArcGIS/rest/services/Aerial/MapServer"/> ... View more

Thanks Dasa, finally got it to work.  Its funny how one space or missing bracket can mess the whole thing up.  One other question.  Apparently the description also honors carriage returns as the <br> tag added an extra space.  Does anyone know a way to make it do single space, the carriage return still leaves it as double space, although this is not a huge problem, it would help the overall size of the popup. Now, that I have that space gone, I think (other than the typing, formatting) I actually like this better as there is more control over how it displays. ... View more

I'm going to have to disagree with you.  Not having the ability to "identify" with popups either using the new popups or the SimpleInfoWidget of past releases is a MAJOR problem for me and no I cannot use it due to the bug.  I shouldn't have to fight with xml just to get it to do something very simple that it is supposed to do.  I already posted the xml files on here and even copied and pasted your example directly and still it did not work.  The main config file is not the problem because it worked just fine at 2.3.1 and when I switch back to the popups without the description, it works just fine (albeit with the bug). I will go ahead and post these but I really don't see how it will help as I have already posted them in the past.  Part of this has to do with the number of fields I am using, but like I said in the previous post there really is no way around this, I need the popup to display this many fields. EDIT: Keep in mind that the PopUp_parcels_description  is incomplete in the description area as I am just trying to make sure it works before I do all of that typing. ... View more

Which one are you working with that works like the popups?  If I can't get this problem fixed, this is enough that I can't use the app and will have to use my 2.3.1 version only.  Problem is that I like some of the new features.  It's a shame that Esri can't seem to write their own software and have to resort to power users like Robert to fix their problems.  Thanks Robert for all you do for the Flex community! By the way, I have copied the code you put above and still no dice.  I think I am ready to just use a different widget and stop using the popups as clearly they aren't usable.  I even looked into decreasing the number of fields I use but it is the way the table comes to me from the county so it would be a huge hassle to pare down the fields everytime I got an update.  However, I would note that the county is working on transitioning to the Orion system so it may look different after that conversion.  Haven't had any updates since June 30, so I have no idea what it will look like. ... View more

I double checked the field name you mentioned in the REST services directory it is correct.  It cuts the n off of the end. That table is not in a geodatabase, I think I just created a dbf file from an Excel spreadsheet.  I'm still getting the Could Not Decode error 1090 from the viewer after removing the other square bracket.  There is something small that it is not liking. <configuration>     <title>{OwnershipRecords.OWNER}</title> <description> <![CDATA [Parcel ID: {OwnershipRecords.PID} <br> Owner: {OwnershipRecords.OWNER} <br> Mailing Address: {OwnershipRecords.MAILADDRES} ]] </description>     <fields>     <field name="OwnershipRecords.PID"/>     <field name="OwnershipRecords.OWNER"/>     <field name="OwnershipRecords.MAILADDRES"/>     <field name="OwnershipRecords.MAILCITY"/>     <field name="OwnershipRecords.MAILST"/>     <field name="OwnershipRecords.MAILZIP"/> <field name="OwnershipRecords.LOT"/> <field name="OwnershipRecords.BLK"/> <field name="OwnershipRecords.TRACT"/> <field name="Subdiv code table.Subdivisio"/> <field name="OwnershipRecords.SEC"/> <field name="OwnershipRecords.TWP"/> <field name="OwnershipRecords.RNG"/> <field name="OwnershipRecords.CALCACRES"/> <field name="OwnershipRecords.PROPNUM"/> <field name="OwnershipRecords.PROPDIR"/> <field name="OwnershipRecords.PROPST"/> <field name="OwnershipRecords.LOTWIDTH"/> <field name="OwnershipRecords.LOTDEPTH"/>     </fields>     <showattachments>true</showattachments> </configuration> ... View more

That still doesn't solve the problem, in fact now I'm getting an error thrown.  I'm using Notepad++ and one of the options allows me to open in IE and it gives me the following message: The XML page cannot be displayed Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later. -------------------------------------------------------------------------------- An opening '[' character was expected. Error processing resource 'file:///O:/acmapflex/popups/PopUp_parcels_description.xml... <![CDATA [[Parcel ID: {OwnershipRecords.PID} ---------^ In the Flex Viewer I get the following error message: http response status: 200 Fault code: Client.CouldNotDecode Fault info: Error #1090 Fault details: null Clearly it has something to do with that opening line, what is CDATA is that C:\Data?  If that's the case it should either be a UNC path or something like Oacmapflex instead of CDATA.  Also I would note that in Notepad++ it highlights the open and close brackets around that first statement as if something is missing. ... View more

This fix will be part of the next release of the ArcGIS Viewer for Flex. One work-around that might help you in the meantime (if you're not OK with using fewer fields, nor with compiling the source code), is to use the <description> tag. From the documentation on Pop-up configuration files: "By default the pop-up window shows the visible fields in a key-value styled table. Alternatively, you can use the <description> tag to present it in a different manner, for example in a sentence or paragraph structure" http://help.arcgis.com/en/webapps/flexviewer/help/#/Pop_up_configuration_files/01m30000002q000000/ I have attempted this but I'm not sure exactly on the format, I can't get it display like I want.  Here's how it is in the example. <configuration>     <title>{NAME}</title>     <description>         <![CDATA[<b>Hurricane {NAME}</b> was a <i>category {CAT}</i> hurricane that occurred in {BASIN} on {TRACK_DATE}. It had a wind speed of {WIND_KTS} knots.]]>     </description>     <fields>         <field name="NAME"/>                 <field name="WIND_KTS"/>         <field name="CAT"/>         <field name="BASIN"/>         <field name="TRACK_DATE">             <format dateformat="shortDateShortTime"/>         </field>     </fields> </configuration> AS of now, this is how I have mine, trying to mimic the sample.  It is ignoring the description part and just filling it out like normal, of course, not working on the second click.  This is a major enough bug that I feel it should be corrected immediately. <configuration>     <title>{OwnershipRecords.OWNER}</title> <description> <![CDATA [[Parcel ID: {OwnershipRecords.PID} <br> Owner: {OwnershipRecords.OWNER} <br> Mailing Address: {OwnershipRecords.MAILADDRES} <br>]> </description>      <fields>         <field name="OwnershipRecords.PID"   alias="Parcel ID" visible="true"/>         <field name="OwnershipRecords.OWNER"   alias="Owner" visible="true"/>         <field name="OwnershipRecords.MAILADDRES"  alias="Mailing Address" visible="true"/>         <field name="OwnershipRecords.MAILCITY"   alias="Mailing City" visible="true"/>         <field name="OwnershipRecords.MAILST"   alias="Mailing State" visible="true"/>         <field name="OwnershipRecords.MAILZIP"    alias="Mailing Zip Code" visible="true"/> <field name="OwnershipRecords.LOT"     alias="Lot" visible="true"/> <field name="OwnershipRecords.BLK"     alias="Block" visible="true"/> <field name="OwnershipRecords.TRACT"     alias="Legal Description" visible="true"/> <field name="Subdiv code table.Subdivisio"     alias="Subdivision" visible="true"/> <field name="OwnershipRecords.SEC"     alias="Section" visible="true"/> <field name="OwnershipRecords.TWP"     alias="Township" visible="true"/> <field name="OwnershipRecords.RNG"     alias="Range" visible="true"/> <field name="OwnershipRecords.CALCACRES"    alias="Acres" visible="true"/> <field name="OwnershipRecords.PROPNUM"    alias="Number" visible="true"/> <field name="OwnershipRecords.PROPDIR"    alias="Direction" visible="true"/> <field name="OwnershipRecords.PROPST"     alias="Street" visible="true"/> <field name="OwnershipRecords.LOTWIDTH"    alias="Lot Width" visible="true"/> <field name="OwnershipRecords.LOTDEPTH"    alias="Lot Depth" visible="true"/>     </fields>     <showattachments>true</showattachments> </configuration> ... View more

Ned,    In the Flex Viewer project right click on src folder in the Package Explorer and choose New > Package and for the name field put com.esri.ags.skins and then paste the PopUpRendererSkin.mxml into that Package/folder and run the Flex Viewer project again. What about those of us using the compiled version?  I don't have an src folder and have no idea what the Package Explorer is.  The compiled viewer is great if you want a canned version of it.  Any customizations apparently require the uncompiled version.  This is not very user friendly for the non-developer crowd. ... View more

I have to agree with Pierre, those of us using the compiled version need the compiled fix.  This is after all the Viewer forum not the API forum. ... View more

I have this strange issue with popups.  They work fine for the first parcel I click on but then for subsequent parcels all I get is the title field and a blank popup with the zoom in link at the bottom.  Any idea why this would happen? ... View more