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

Selection Widget Updated Version

MarkHoyland

The Selection widget has a "Select by Attributes" and "Select by Location" option similar to ArcGIS.
Widget link: http://www.arcgis.com/home/item.html?id=20ed6af9ab204548bbf092d51b51fef8

Version 1.5 of the widget replaces version 1.0

Enhancements and fixes include:
*Each time a query layer was added it was also being added to the TOC. This has been fixed.

*When resizing the widget, the datgrid would not resize properly. This has been fixed.

*Uses paging for selection of unique value list. This means that ALL values will be parsed regardless of the ArcGISServer setting to limit responses. There is an option to ESC out of a large query. (This is only for the Unique list, not getting features).
I have included an ESRI TaxParcel Layer that has 18,000+ records. Get Unique Values on the PSTLSTATE field to see this in action.
Available on my example site. The URL is on the Widget download page.

*Aliases can now be used. It will now use the Alias as set in the Featureclass. You can also override the Alias in the SelectionWidget.xml config file.

*ArcGis layers that have joined tables will now work with fully qualified field names. (thanks Dasa for the idea)

*Styling for selection colours has been documented in the SelectionWidget.xml config file (example provided).

*Styling for datagrid has been changed. It can now also be styled in SelectionWidget.xml config file (example provided). (thanks Mehul for the idea)

*Changed initial uniquevalue query to use "text='%'" instead of "where '1=1'" for Mike.:)

*You can now override scale range for layers.

*Link field now has a prefix/suffix option in the SelectionWidget.xml config file (naming convention the same as Robert SCheitlin's esearch widget)

*Shape_area and Shape_length can be used in the fields.

Link to previous thread :http://forums.arcgis.com/threads/24151-Selection-Widget-for-SFV2.2-(with-a-query-builder)

タグ付けされた投稿をもっと見る

Accepted answers

All comments

AngieAllison

Did anyone get the dates problem working in this widget. HELP please i am in great need of this widget or some widget to query data in FELX !!!

AlKamuda

Hey did you get to the bottom of this one?

I want to say that when I got the error I was able to make it stop by adding the InfoPopupWidget. The code for the Selection widget has a line that calls for the InfoPopupWidget and in viewer 3.1 its not there - you need to add it the viewer under widgets/InfoTemplates/

hope this helps

CatherineEnnis

Anyone have an idea about the error #2124?

Hey did you get to the bottom of this one?

ScottMcGee

Just wondering...

Where can I get the Info Popup widget? I searched the ArcGIS Resources Flex sample gallery and didn't see it there.

Update (30 seconds after I posted my message) - As soon as I posted my message I saw that you had just now uploaded the Info Popup Widget.

Thanks much!

AlKamuda

i'm no expert in doing a recompile (trial / learn by fire)and since I was able to make it work on my flex 3.1 test site. I'm in the process of upgrading my internal site from 2.3 to 3.1 and it tested fine in my test setup. You will need to add InfoPopupWidget to your widgets for this to work.(i've included this as well)
Attached is an uncompile and compiled version that works in 3.1 on my setup.

Use at your own risk and I assume no resposibility since I started off by saying "i'm no expert"

Selection.zip

InfoTemplates.zip

rzufelt

Seemed to be working for me without removing the glow filter. However, then I tried it with "my" selection colors. Turns out that yellow is the glow color, so didn't notice it with your colors at first.

However, if I remove the glow filter (make sure to add the new function AND update the other one to call the removeGlow) then whatever color I select gets applied.

I did notice that if you set an alpha="0.0", it will override with the defaults, so, in order to "turn off" the polygon fill color, I had to change the mxml to default to 0.0.

Also, it does not appear as if the datagrid colors are being applied at all, I just keep that section commented out.

R_

CarolineCochrane

Hi,

I have this latest version of the SelectionWidget working well in my v3.0 viewer. Although Im not sure how to show the polygon results as highlighted (yellow) as previously did in the older version.

I changed the SelectionWidget.xml like below, but this doesnt seem to be picked up. I have deleted any web storage settings and also tried Roberts suggetsion of adding the new function removeGlow but this also did not work for me.

Any suggestions at all very welcome! 🙂

All the best,

Caroline

<?xml version="1.0" ?>
<configuration>



<symbols>
<picturemarkersymbol height="30" width="30" xoffset="0" yoffset="0"
    url="widgets/Selection/assets/images/i_pin3.png" />

<simplelinesymbol color="0xffd700" alpha="0.8" width="2" />

<simplefillsymbol color="0xffd700" alpha="1">
   <outline color="0xffd700" alpha="0.8" width="2" />
</simplefillsymbol>
</symbols>



<datagrid   alternatingColor1="0xeff3fa"
    alternatingColor2="0xffffff"
    backgroundAlpha="0"
    horizontalGridLines="true"
    horizontalGridLineColor="0x666666">
</datagrid>

rzufelt

OK, I had a type in my useutc="true" option in my popupconfig.xml, so now the built in popups report the correct date as well as the esearch widget.

Got the format of the date in selectionwidget, but it is still 1 day behind and the export shows the long date. Will let you know if I find a solution.

R_

AngieAllison

that is what i have going on as well. how do i fix this?? something with utc date. and the export still has that long number as the date??

rzufelt

I didn't see anywhere that the date format was being passed from the xml to the swf so I had to add it to get the format to take affect with the selection widget.

Interesting about the day off. If I use the selection widget OR just click on a feature that I have a popupconfig for, the date is one day behind what is in the actual data.
Also, if the data is null, it reports 12/31/1969.

However, Roberts eSearchWidget reports the correct date.

R_

AngieAllison

i still do not have the date issue resolved. this UTC? it is showing the day before in this widget and all other widgets are fine with this string added
<field name="INSTALLDATE" dateformat="MM/DD/YYYY" useutc="true"/>

RobertScheitlin__GISP

Jefferson,

Well many people make the same mistake, that they can comment out something that they believe is not important because they don't think they are using it. Even though I mentioned that the InfoPopup is old (maybe not the appropriate wording) . It is really still very much used if the widget builder chooses to use it instead of the newer popup. Lesson to learn from this is leave everything that the widget builder had in the XML and only replace what is necessary to use your data and get the widget working then one by one eliminate things that you believe that are not needed.

JeffersonFerreira_Ferreira

Jefferson,

The error you are getting means "Loaded file is an unknown type". I have seen this in the past when a widget is using the old infoPopup and someone mistakenly omits that line from the config xml for the widget. So do you have this line towards the bottom of your SelectionWidget.xml?
    <zoomscale>5000</zoomscale>
    <info>widgets/InfoTemplates/InfoPopupWidget.swf</info>
</configuration>
And if so are you sure that the widgets/InfoTemplates/InfoPopupWidget.mxml is added to the modules list of your flex viewer project so that it is being compiled to a swf?

rscheitlin;

These <zoomscale> and <info> tags are all commented. In fact I have a infoTemplates folder in my widgets folder, but, obviously, I dont use it. But this InfoPopup is not part of flex 2.5, right? How you said its an old element. Nevertheless I'll try to include it in modules list and see what happens.
Soon I'll post the result.

thanks

RobertScheitlin__GISP

Jefferson,

The error you are getting means "Loaded file is an unknown type". I have seen this in the past when a widget is using the old infoPopup and someone mistakenly omits that line from the config xml for the widget. So do you have this line towards the bottom of your SelectionWidget.xml?

    <zoomscale>5000</zoomscale>
    <info>widgets/InfoTemplates/InfoPopupWidget.swf</info>
</configuration>

And if so are you sure that the widgets/InfoTemplates/InfoPopupWidget.mxml is added to the modules list of your flex viewer project so that it is being compiled to a swf?

rzufelt

Not sure what to tell you.

I just re-downloaded the SelectionWidget v1.5, added to a new FlexViewer3 project (uncompiled version), added to my module list and let it build.

I do get warning about the dispatchEvent, but if I ignore it, and do NOT make any changes (as I did above)(it seems the changes remove a warning, but don't affect functionality), it seems to be working just fine. even with the SelectionWidget.xml that came with it, though I am not loading any of the services selected in my map.

Once I change the config to my services, it is still working fine.

Have not seen the error you mention and can't seem to reproduce.

R_

I am using IE8, Flash Builder 4.6 and the 4.6.0 SDK

rzufelt

Hmm, if I get a chance, I'll try to re-do what I did as I still have yet to get the error.

Maybe I changed something else that I forgot about.

R_

JeffersonFerreira_Ferreira

I do not get any errors. Just a few warnings about length not being bindable.

R_

There are many people receiving this error #2124. The widget works fine, every first open it presents this message. I reviewed all the xml and mxml and can't identify what could be wrong.

rzufelt

I do not get any errors. Just a few warnings about length not being bindable.

R_

JeffersonFerreira_Ferreira

I have updated this part of the init() function and it seems to be working fine in 3.0: Keep in mind that I am no pro by any means, but this seems to work.

     for (var i:int = 0; i < lyrList.length(); i++)
     {
      var lyrURL:String = lyrList.url;
      var lyrLabel:String = lyrList.name;
      
      var featureLayer:FeatureLayer = new FeatureLayer(lyrURL);
      featureLayer.name = lyrLabel;
      var l1lst:XMLList = (lyrList.maxscale as XMLList)
      var l2lst:XMLList = (lyrList.minscale as XMLList)
      
      //Override the min and max zoom scale if they are in the config   // not sure why couldn't test directly but had to create varable first???
      if (l1lst.length() > 0 )
       featureLayer.maxScale = lyrList.maxscale;
      if (l2lst.length() > 0 )
       featureLayer.minScale = lyrList.minscale;
      
      featureLayer.addEventListener(LayerEvent.LOAD, featureLayer_loadHandler);
     }
     
.........
........
........
     //ViewerContainer.dispatchEvent(new AppEvent(AppEvent.DATA_CREATE_INFOWIDGET, data, infoReady));
     AppEvent.dispatch(AppEvent.DATA_CREATE_INFOWIDGET, data, infoReady);

I still get a couple warnings about "Data binding will not be able to detect assignments to length" for the end of SelectByAttributes.mxml and SelectionResults.mxml but it is working.

R_

Is it for the error #2124??

rzufelt

I have updated this part of the init() function and it seems to be working fine in 3.0: Keep in mind that I am no pro by any means, but this seems to work.

     for (var i:int = 0; i < lyrList.length(); i++)
     {
      var lyrURL:String = lyrList.url;
      var lyrLabel:String = lyrList.name;
      
      var featureLayer:FeatureLayer = new FeatureLayer(lyrURL);
      featureLayer.name = lyrLabel;
      var l1lst:XMLList = (lyrList.maxscale as XMLList)
      var l2lst:XMLList = (lyrList.minscale as XMLList)
      
      //Override the min and max zoom scale if they are in the config   // not sure why couldn't test directly but had to create varable first???
      if (l1lst.length() > 0 )
       featureLayer.maxScale = lyrList.maxscale;
      if (l2lst.length() > 0 )
       featureLayer.minScale = lyrList.minscale;
      
      featureLayer.addEventListener(LayerEvent.LOAD, featureLayer_loadHandler);
     }
     
.........
........
........
     //ViewerContainer.dispatchEvent(new AppEvent(AppEvent.DATA_CREATE_INFOWIDGET, data, infoReady));
     AppEvent.dispatch(AppEvent.DATA_CREATE_INFOWIDGET, data, infoReady);

I still get a couple warnings about "Data binding will not be able to detect assignments to length" for the end of SelectByAttributes.mxml and SelectionResults.mxml but it is working.

R_

JeffersonFerreira_Ferreira

Anyone have an idea about the error #2124?

MikeDahm

Any plans for this widget to be updated for Flexviewer 3.0?

rzufelt

Thanks again Robert, works like a charm.

No wonder I couldn't figure it out. Guess I should have tried a color that blends with yellow to make cyan 🙂

R_

RobertScheitlin__GISP

Rhett,

This is because the selection widget uses a feature layer in selection mode and the default selectioncolor is yellow which is applied as a filter that blends with the symbol color. To fix this just make these changes in the selection widget:

//New function
            private function removeGlow( fl:FeatureLayer ):void
            {
                var len:int = fl.numChildren;
                var dObj:DisplayObject;
                for ( var i:int = 0; i < len; i++ ) {
                    dObj = fl.getChildAt( i );
                    if ( dObj.filters ) {
                        dObj.filters = [];
                    }
                }
            }
            //Updated function
            protected function featureLayer_selectionHandler(event:FeatureLayerEvent):void
            {
                removeGlow(event.featureLayer);
                
                dispatchEvent( new Event( 'featurelayer_selection', true ) );
                
                var flEvent:SelectionFeatureLayerEvent = new SelectionFeatureLayerEvent(
                    SelectionFeatureLayerEvent.LAYER_RESULTS,event.featureLayer);
                dispatchEvent(flEvent);
                
                if (event.type == FeatureLayerEvent.SELECTION_CLEAR)
                {
                    this.showInfoWindow(null);
                }
                
            }

rzufelt

I am trying to get the selection outline color to match that of my eSearch widget. The coding is very similar, but does not seem to work correctly in the SelectionWidget.

If I don't change it in the config.xml or hard code in the mxml, I get the default browinish color. If I change it in the config.xml or the mxml, it turns to a green color, no matter what I set it to (red, black, white, etc. always is the same green color). In the eSearch widget I set it to 0x00FFFF and get a nice light blue outline.

Has anyone figured out how to make this change "take effect" in the SelectionWidget?

Any ideas,

R_

JeffersonFerreira_Ferreira

Hi all;

No problems with the operation of the tool. However when we opened for the first time an error message appears. The Error #2124 window appear (see attached file), then we close and the tool works normally. What could be happen? Any suggestions?

Untitled.png

JeffersonFerreira_Ferreira

Dear Colleagues;

Please, let me ask you a question (apparently simple) about the Selection Widget. Maybe 'cause my "middle-of-the-road" english understanding or 'cause the lack of familiarity with sql spatial operators, Im facing difficulties to distinguish between "that are completely within" and "that are is (fully) inside". For me this statement appear to have a grammatical error in "that are is...". I've searched a lot at the internet but cant find this specifically issue. If you could clarify me I'll be grateful.

Thanks

mburge

Mark,
Does 2.5 version have an uncompiled component? If so, where can I find it to download? Thanks

mburge

Sorry, meant to say "uncompiled".

mburge

Mark,
Is there an uncompile version of this widget? And what is the latest version? Is there a 2.5 version? Thanks

会話に参加する

サインインしたメンバーは投稿、更新のフォローなどができます。初めてですか？無料アカウントを登録してください。

クイックリンク

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