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; } } }

Table of Contents - Legend Widget for FlexViewer 2.x

RobertScheitlin__GISP

All,

Here is the next in my line of widgets for the FlexViewer 2.x.

The legend portion of this widget is the same code as my dynamic legend widget so,

IT IS FOR ARCGIS SERVER 10 OR GREATER ONLY

This is just a simple TOC Widget that includes my dynamic legend component.
This widget also includes my enhancement for map service transparency,
right click context menu for zoom to make layer visible, and my scale
dependent renderer for the TOC checkboxes.

Vind meer berichten getagd met

Accepted answers

All comments

MicahWilliamson

Nope, not anymore. Bad coding on my part. :cool:

Hey Mike!

-

ErikMartin

Robert,

Is there a way to exclude FeartureLayers from the TOC widget? I've messed around with the order in TOC.as, following your message above to Jim, but have not figured out how to exclude them altogether.

Thanks, as always!
-Erik

RobertScheitlin__GISP

Erik,

Excluding layers is as simple as this:

<excludelayer url="http://sampleserver1.arcgisonline.com/ArcGIS/rest/services/Louisville/LOJIC_LandRecords_Louisville/MapServer" id="0"/>

An example straight from the IdentifyWidget.xml that come with the download.

RhettZufelt

Or an example from the TOC widget config:

  <excludelayer mapservice="Earthquakes"></excludelayer>
  <excludelayer mapservice="Fires"></excludelayer>

Or like this to ONLY exclude sublayer 0 and 1 if dynamic:

  <excludelayer mapservice="Earthquakes">0,1</excludelayer>

ErikMartin

The contents of my TOCWidget.xml now read:

<configuration>
 <labels>
  <visibilitylabel>Layer Visibility</visibilitylabel>
  <zoomtoextent>Zoom To Layer Extent</zoomtoextent>
  <expandall>Expand All Layers</expandall>
  <collapseall>Collapse All Layers</collapseall>
  <zoomtomakevisible>Zoom To Make Visible</zoomtomakevisible>
  <generatinglegendmsg>Generating TOC Legend</generatinglegendmsg>
 </labels>
 <tocsettings>
  <expanded everything="false">false</expanded>
  <collapselegends>true</collapselegends>
  <disablezoomtomenuoption>true</disablezoomtomenuoption>
 </tocsettings>
 <legendtimeout>10</legendtimeout>
 <excludelayers>
  <excludelayer url="http://maps.myserver.com/mapstest/rest/services/Project/Test/MapServer" id="1"/>
 </excludelayers>
 <excludegraphiclayers>true</excludegraphiclayers>
 <excludebasemaplayers>true</excludebasemaplayers>
 <usenewesridescription>false</usenewesridescription>
</configuration>

I also tried

<excludelayer mapservice="Layers">1</excludelayer>

With both configurations, Layer 1 from my map service is still showing p in the TOC. More significantly, the FeatureLayer that is created from MapService Layer 1 in AS & added to the map (via a separate custom widget) is showing up in the TOC as "FeatureLayer774". Then, when I remove that FeatureLayer from the map via AS, the TOC throws an error:

TypeError: Error #1009: Cannot access a property or method of a null object reference.
 at widgets.TOC.toc.tocClasses::TocMapLayerItem/filterOutSubLayer()
 at widgets.TOC.toc.tocClasses::TocMapLayerItem/processLegend()
 at Function/<anonymous>()
 at flash.events::EventDispatcher/dispatchEventFunction()
 at flash.events::EventDispatcher/dispatchEvent()
 at HTTPOperation/http://www.adobe.com/2006/flex/mx/internal::dispatchRpcEvent()
 at mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::resultHandler()
 at mx.rpc::Responder/result()
 at mx.rpc::AsyncRequest/acknowledge()
 at DirectHTTPMessageResponder/completeHandler()
 at flash.events::EventDispatcher/dispatchEventFunction()
 at flash.events::EventDispatcher/dispatchEvent()
 at flash.net::URLLoader/onComplete()

Is there something obvious I'm missing?

RhettZufelt

This is what I found to keep a MapService loaded as type="feature" from displaying in the TOC widget:

<excludelayers>
     <excludelayer mapservice="Layers"></excludelayer>
</excludelayers>

Do not put put the sublayer id in there with a type="feature" or it will only remove "part" of it from the TOC (I.e., I still see it, just won't turn on/off and no symbology or plus sign).

I have randomly been getting null value errors as well, reload without change, and it works fine (does not work in Chrome) and the version 3.1.5 errors out for me a fraction of the time compared to 3.2.

Didn't have these issues until I tried to exclude a feature layer, so may be related to this somehow.

Do you have the LayerList widget active, or maybe the mapswitcher "More" button? I notice that if I try to enable the layerlist, I get errors much more often.

Anyway, time to go for the weekend, no more testing until Monday. However, I have tested the excludelayer coding above and works for me.

R_

Since you are adding the featurelayer other than the main config, have you tried this:

<excludelayer mapservice="FeatureLayer774"></excludelayer>

perhaps your code only adds a layer name and not an ID? It is my understanding it needs an id to be programatically searched for.

fLayer.name = dLayer.id = item.name; worked for me in a previous widget to see layers added by another.

KennyWebster

Hi all,

I've noticed some odd behaviour related to the zoom to menu option.

We're using Flex Viewer 3.0 along with version 3.0 of the TOC widget.

What I've been able to identify is that when the disablezoomtomenuoption is set to false in the config things seem to work ok. However we would like to set it to true. The behaviour we've noticed is that the menu option is disabled entirely (the button doesn't exist to click) if the layers are visible (user is zoomed in). When the user zooms out to where a layer is no longer visible, the menu option will reappear and allow the user to zoom to visible, I believe this is all by design. Now this is where things get a little quirky. We have a handful of layers (~5) which do not disable the menu button once they become visible. However, the button cannot be clicked, it doesn't work. For the rest, all works as described above.

My first thought is that it has something to do with the those specific layers. But as of yet I have been unable to find a pattern they relates the offending layers and differs them from every other layer.

If anyone has any suggestions on what direction I should be going here to fix this I would be greatly appreciate it!

JasonStanton__GISP

Robert,

I posted this question a couple of weeks ago. I'm guessing you just missed it so I wanted to follow-up.

Have you ever considered adding the ability to save legend properties similar to the eBookmark or eDraw widget? For example if the user has turned layers on/off or set transparencies they could save those 'settings' and load them back in later? I'm not even sure that's possible, but one of our communities asked for this.

If you could let me know either way I would greatly appreciate it. Thanks!

Jason

RobertScheitlin__GISP

Jason,

No I have really not considered that. It seems like a lot of work for a minimal return. It could be done in code as I believe that the setting of a layers visibility programmatically is now captured in the toc (i.e. checked or not, this was a issue before). I can not say I will be considering this as an enhancement though as I currently have no free time.

RobertScheitlin__GISP

Kenny,

I believe that the zooming issue was fixed in a newer release. As you are speaking of a version of the widget that is now 2 versions behind I won't be able to help with bugs on that version.

JasonStanton__GISP

Robert,

Thanks for getting back to me. To be perfectly honest I had not idea if it was something that would take 3 minutes or 3 weeks so I thought I would ask. I completely understand your time limitations.

Jason

DerekHunter1

GIS Dev,

I have a Beta version right now that does all of it in the widget. This link is to the compiled widget, but if you want to test it out I would appreciate and input.

http://forums.arcgis.com/threads/75331-Legend-Widget-not-Refreshing?p=267156&viewfull=1#post267156

Robert,

We are using the Identity Manager built into ArcGIS Server for users to login to secured services in Flexviewer 3.0. The TOC Widget works fine (3.0), but none of our services' served using an Identity manager login have their Legend swatches displayed in the TOC. Would the updates to the current widget address this?

I added a token to the url in the main config, but still none of the swatches display. Viewing traffic through Firebug I see:
{"error":{"code":499,"message":"Token Required","details":[]}}, so I am very confused.

Thoughts?

Derek

RobertScheitlin__GISP

Derek,

The latest versions do handle secured services using Identity Manger log in.

MicahWilliamson

Robert:

I have read posts where you fixed the group layer issue in version 3.1.5 and above. I am using version 3.2 with Nested groups and am experiencing issued with layers turning on and off. I would give you a link to the REST endpoint but unfortunately it is not exposed. Here is a link to the screencast of the issue:
http://screencast.com/t/ClTsDb5UQeP8
This is a fresh install of the compiled code straight into the widgets folder, no modifications.

Please take a look and advise. should i break out these groups into separate services?

-Micah

LewisLock

The layers in the TOC always appear in a random order, is there any way to make them stop doing that? Sorry if this question has already been answered, I could'nt find it. Lewis.

RhettZufelt

The layers in the TOC are in the reverse order that they are listed in the main config.xml.

So, the first layer listed under <operationallayers> will be at the bottom of the TOC, the last layer in the <operationallayers> section will be at the top of the TOC.

R_

RoseZhou

Hi,

When I clear my browser cache and launch my FlexViewer, then open the TOC widget, I got following ActionScript error:

TypeError: Error #1009: Cannot access a property or method of a null object reference.
at widgets.TOC.toc.tocClasses::TocMapLayerItem/createChildren()
at widgets.TOC.toc.tocClasses::TocMapLayerItem()
at widgets.TOC.toc::TOC/registerMapLayer()
at Function/<anonymous>()
at widgets.TOC.toc.utils::MapUtil$/forEachMapLayer()
at widgets.TOC.toc::TOC/registerAllMapLayers()
at widgets.TOC.toc::TOC/commitProperties()
at mx.core::UIComponent/validateProperties()
at mx.managers::LayoutManager/validateProperties()
at mx.managers::LayoutManager/doPhasedInstantiation()
at mx.managers::LayoutManager/doPhasedInstantiationCallback()

If I refresh the FlexViewer and re-launch the TOC widget, it works fine.

Any ideas? Thanks in advance!

Rose

LewisLock

The layers in the TOC are in the reverse order that they are listed in the main config.xml.

So, the first layer listed under <operationallayers> will be at the bottom of the TOC, the last layer in the <operationallayers> section will be at the top of the TOC.

R_

Appreciate the response. For the most part that is quite true, but often the ordering is ignored. I wonder if it has something to do with different layers loading up at different rates? Sigh.

RhettZufelt

Have you made any customizations to your FV app? I can't reproduce your issue.

If I put some services in there that take a long time to load, it just takes longer to load my FV app, but the order in the TOC remains the same.

Perhaps someone else has experienced this issue and can help.

R_

What version of FV and TOC widget are you using? What "type" of layers are you loading? Are you trying to use the LayerList widget and/or MapSwitcher="true" as well?

GISDev1

Hi,

When I clear my browser cache and launch my FlexViewer, then open the TOC widget, I got following ActionScript error:

TypeError: Error #1009: Cannot access a property or method of a null object reference.
at widgets.TOC.toc.tocClasses::TocMapLayerItem/createChildren()
at widgets.TOC.toc.tocClasses::TocMapLayerItem()
at widgets.TOC.toc::TOC/registerMapLayer()
at Function/<anonymous>()
at widgets.TOC.toc.utils::MapUtil$/forEachMapLayer()
at widgets.TOC.toc::TOC/registerAllMapLayers()
at widgets.TOC.toc::TOC/commitProperties()
at mx.core::UIComponent/validateProperties()
at mx.managers::LayoutManager/validateProperties()
at mx.managers::LayoutManager/doPhasedInstantiation()
at mx.managers::LayoutManager/doPhasedInstantiationCallback()

If I refresh the FlexViewer and re-launch the TOC widget, it works fine.

Any ideas? Thanks in advance!

Rose

Any news on this?

RobertScheitlin__GISP

GIS Dev,

Hard to respond to something I can not duplicate.

GISDev1

GIS Dev,

Hard to respond to something I can not duplicate.

Indeed.

For my particular issue with the createChildren error, I tracked it down to a problem REST service (10.1.1) which is identical in almost every way, except for the spatial data, to a similar service which works just fine. The pop-ups had no change on if I got the createChildren error or not. I checked the code that sarthakdatt used in the fix on github (https://github.com/Esri/arcgis-viewer-flex/commit/2c9ea4642711e3fabc49f5cd6d6cf967ada9b2e3), and your TOC V3.3.0 of course already had that fix implemented.

My problem service does return "arcGISDynamicMapServiceLayer.visibleLayers == null"
and that was causing the error. This only occurs in IE, and not other browsers. Both debug flash players are fully up to date.

I added a simple if check for null and all is well now. I have no clue why that one particular service returns null for visible layers in the class, as the service works as expected in all other accounts, and there are default layers that are on in the MXD that show up just fine when turning on the layer in the TOC in Flex. I'm going to look into the issue further when I have more time.

JeffLegato

Robert:

I have read posts where you fixed the group layer issue in version 3.1.5 and above. I am using version 3.2 with Nested groups and am experiencing issued with layers turning on and off.

Robert,

I am experiencing the same issue however I am using 3.3 in the Application Builder.

I have a service you can use to test...

http://www.sloplanning.org/arcgis/rest/services/Planning/test/MapServer

To duplicate what I am seeing:
1. Load the layer into a flexviewer app
2. Check on the "Land Use" group
3. Zoom in 2 levels and watch it turn off
4. Check it back on and zoom in one more level to see black land use outlines appear
5. Zoom back out until they disappear
6. Notice that the Land Use group is now unchecked

I worked around this behavior by republishing the service with the Land Use group turned on in the MXD.

On another note (but related) a user can't turn on a group if nothing is checked on within it. Is this fixable?

Thanks again for taking some time on this. Much appreciated!

RobertScheitlin__GISP

Jeff,

OK, I am not sure I am understanding the instructions... When I check the 'Land Use' on the Land Use Outlines are not visible based on scale. When I zoom in three times they become visible. This is all accurate based on design and scale dependency.

JeffLegato

Jeff,

OK, I am not sure I am understanding the instructions... When I check the 'Land Use' on the Land Use Outlines are not visible based on scale. When I zoom in three times they become visible. This is all accurate based on design and scale dependency.

Correct, but when I zoom back out they not only disappear, the Land Use group layer becomes unchecked.

RobertScheitlin__GISP

Jeff,

Which version of the widget are you using?... I do not see the layer get unchecked using 3.3.

JeffLegato

I downloaded the 3.3 version and am using it with the ArcGIS Viewer for Flex Application builder Version 3.3. I am attaching a screen shot of the download contents...
[ATTACH=CONFIG]25613[/ATTACH]

I tried using the compiled_FV3.3 widget in the same download but that didn't make any difference.

Thanks for all you do by the way! Your time and effort in this benefits us all.

Capture.PNG

RobertScheitlin__GISP

Jeff,

I don't know what to tell you... Here are the screen shots of what I see.

[ATTACH=CONFIG]25619[/ATTACH][ATTACH=CONFIG]25620[/ATTACH]

preview-1.jpg

preview-2.jpg

JeffLegato

Robert,

I was able to publish this temporarily on our public facing server: http://www.sloplanning.org/test/test/

I think you will be able to see what I am experiencing there. Specifically, it's the Land Use group layer that is having troubles.

Thanks again!

RhettZufelt

Jeff,

Hard to test as your crossdomain is blocking me.

However, curious if you still have the issues if you set the mapswitcherwidget.xml layerlist tag to false? <layerlist visible="false"> since the TOC widget is not designed to run with it set to true?

R_

Guess it is only blocking the gis1:6080 stuff.

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

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