nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

2.4 PopUp scrollbar bug

DasaPaddock

A bug has been found in the 2.4 release where if you have many fields shown and the scrollbar appears in the PopUp, it only works the first time the PopUp opens. The second time it opens, only the title is shown. The field area is blank. The fix for this is in the attached PopUpRendererSkin.

Here's more information about how to use "custom" skins:
http://help.arcgis.com/en/webapi/flex/help/index.html#/Styling_and_skinning_overview/017p0000001s000000/

PopUpRendererSkin.mxml.zip

Clip_228.jpg

IMG_1444.jpeg

Najděte více příspěvků označených jako

Accepted answers

All comments

RobertScheitlin__GISP

Kevin,

Look here under bug fixes:

http://help.arcgis.com/en/webapi/flex/help/index.html#/What_s_new_in_ArcGIS_API_for_Flex/017p0000000w000000/

KevinHigh

Is this fixed in 2.5?

MeghanMcGaffin

For my <description>, I just use one long line of code with tags between each new line

This is a quick workaround.

Thanks

After banging my head for some time now this workaround has fixed my issue! Many many thanks!

GrayRackley

For my <description>, I just use one long line of code with tags between each new line:

Code:
<description><![CDATA[Bluff Level: {BluffLevel} Failure Date: {FailureDate} Description: {Description} Elevation: {Elevation} ft USACE Reach: {USACE_Reach} Image: <a href="http://gisweb:9231/bluffexplorer/bluff_photos/bluff_failure/{Picture}.jpg">{Picture}</a>]]></description>This works perfectly for me. See the attached picture for the example

This is a quick workaround.

Thanks

GregoryPierce

Adding to what Jay said:

Once you copy the PopUpRenderSkin.mxml into the com.esri.viewer.skins folder

add the following to the defaults.css file in src->default package

esri|PopUpRenderer
{
skinClass:ClassReference("com.esri.viewer.skins.PopUpRendererSkin")
}

compile the project and run

Subu

Thank you! I thought I was going crazy trying to figure out how to implement that skin!

KevinHigh

Ari-

For my <description>, I just use one long line of code with tags between each new line:

 <description><![CDATA[Bluff Level: {BluffLevel}<br>Failure Date: {FailureDate}<br>Description: {Description}<br>Elevation: {Elevation} ft<br>USACE Reach: {USACE_Reach}<br>Image: <a href="http://gisweb:9231/bluffexplorer/bluff_photos/bluff_failure/{Picture}.jpg"><u>{Picture}</u></a>]]></description>

This works perfectly for me. See the attached picture for the example

EDIT: The code above is supposed to be one long line, but somehow got wrapped when I posted it.

Popup_Example.jpg

Screenshot 2024-07-16 at 9.14.26 AM.png

AriIsaak1

Has anyone figured out the extra space issue when using the description workaround? doitjd1 mentioned a tag. Can you go into a bit more detail on this? on every line or what.

I agree the popup shouldn't have been integrated into the release if it didn't function right. Then again set datasources in ArcCatalog finally works at 10. I think it was integrated in 8.2.

SubramanianSwaminathan

Adding to what Jay said:

Once you copy the PopUpRenderSkin.mxml into the com.esri.viewer.skins folder

add the following to the defaults.css file in src->default package

esri|PopUpRenderer
{
skinClass:ClassReference("com.esri.viewer.skins.PopUpRendererSkin")
}

compile the project and run

Subu

Thanks Dasa,

I had not yet worked with custom skins before so it took a little while to understand how to apply what was described in the API documentation to the viewer. Once I put the the new skin file in the com.esri.viewer\skins folder and the reference in the defaults.css file the fix worked great.

Thank you,
Jay

JayBoyd

Thanks Dasa,

I had not yet worked with custom skins before so it took a little while to understand how to apply what was described in the API documentation to the viewer. Once I put the the new skin file in the com.esri.viewer\skins folder and the reference in the defaults.css file the fix worked great.

Thank you,
Jay

jamesdiaz

worked for me

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 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.

JoshWhite

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 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.

DasaPaddock

There's an extra space in this line:
<![CDATA [Parcel ID: {OwnershipRecords.PID} 

It should be:
<![CDATA[Parcel ID: {OwnershipRecords.PID}

JoshWhite

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.

configs.zip

Untitled.jpg

RobertScheitlin__GISP

Josh,

There is no issue/bug with the popups besides the one that Dasa has posted about that should be preventing you from using the popups. Many users and I are successfully using the popups without code changes, just xml configuration. Your issue with not getting the popups to work at all has to be something simple that you are missing. The next step in diagnosing this is for you to post your whole main config.xml and your whole popups/PopUp_???.xml files. Probably best to zip them up and post them. The API team does a great job with this software and listens to the users as far as improving and adding features we are looking for, but what software company fixes a bug the next day or week based a small issue that only limits one small aspect of there overall software usability?...

JoshWhite

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.

PierreLarondelle

The easiest way I found to workaround the issue is to use Robert's Enhanced widgets. It's working very well with a few customizing to bring it to your needs. Yes it needs to rewrite some XML's but it's worth it, imho.

I can't wait a bunch of weeks for the next release of the viewer for just a recompiling with the corrected code if I understand well. I'm lonely working on building / developing a small city GIS from scratch and every minutes counts. Nonetheless, if developpers succeed in convincing my direction to gently wait for me 'till 2.5 is released, they're welcome ! 😉

I will need to begin to approach Flex environment as gaining a bit of independence in the future will be a must.

Have a nice day, All.

RobertScheitlin__GISP

Josh,

Try copying exactly what I have here. Every time you seem to add a new little syntax error. The items indicated in red have to be there.

<?xml version="1.0" ?>
<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>

JoshWhite

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>

RobertScheitlin__GISP

Josh,

I did not notice until now that you have an extra square bracket at the begining of your CDATA. Try this:

<?xml version="1.0" ?>
<configuration>
    <title>{OwnershipRecords.OWNER}</title>
    <description>
    <![CDATA [Parcel ID: {OwnershipRecords.PID} <br>
    Owner: {OwnershipRecords.OWNER} <br>
    Mailing Address: {OwnershipRecords.MAILADDRES} <br>
    Continue to add all your fields here: {OwnershipRecords.???} <br>]]>
    </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" />
        <!-- I am wondering about the above field name is that correct? -->
        <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>

JoshWhite

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.

RobertScheitlin__GISP

Josh,

The part about the info not showing on the second click is the bug that you are aware of, the rest of the issue you are having is related to improper configuration.

Notice in the sample that you listed all of the fields are used in the description tag and each of the fields listed under the fields element only have the attribute of name.

<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 stated in the documentation: http://help.arcgis.com/en/webapps/flexviewer/help/index.html#/Pop_up_configuration_files/01m30000002q000000/

Use either <description> or <fields> for the main content.

You wound need something more like this:

<configuration>
    <title>{OwnershipRecords.OWNER}</title>
    <description>
    <![CDATA [[Parcel ID: {OwnershipRecords.PID} <br>
    Owner: {OwnershipRecords.OWNER} <br>
    Mailing Address: {OwnershipRecords.MAILADDRES} <br>
    Continue to add all your fields here: {OwnershipRecords.???} <br>]]>
    </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>

JoshWhite

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>

BjornSvensson

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/

JoshWhite

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.

PierreLarondelle

Hello All,

Thanks for already debugging this issue (I encounter it end of last week) but as we are not all Flex experts, could anybody be kind to give access to a compiled version of the solved problem in order to put the solution directly in the flexviewer tree ?

And, as it is a bug, it would maybe also nice to provide us a fixed version of the flexviewer 2.4 to download from the website ... 😉

Anyway, thanks a lot for the very usefull work done here !

Pierre.

Připojte se k diskusi

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.