Latest Contributions by TonghuiMing

@RyanBohan Thanks for the suggestion. We will take them into consideration when evaluating the ENH directions and possibilities. Tonghui ... View more

@DavidColey Yeah, I would say it could provide a better experience for users. Here is another case similar to what you mentioned: In Map Viewer, if you only click on the map, the behavior follows what I described above; however, if you open the Attribute Table, then click on the map, the selection becomes multi-selection with all 25 results highlighted. It means that the AT here overwrites the popup behavior and then did something extra to handle this case. This could be something we can think about for ENH in the near future. Thanks for your valuable input. ... View more

@MarceloRosensaft - unfortunately we have not supported this and probably will not support it for the time being. Providing a "Select all" feature can be risky when the data amount is too large (say over 1 million) and then using it will cause performance issues, even crash the app. ... View more

Hi @RyanBohan  When you see the map popup which includes 168 features, it does not mean all these features are selected. It represents that clicking on a point gives you the adjacent potential results by a certain range, while only one of them - the highlighted one is currently in the selection queue. Notice that if you click the left/right arrow keys, the selection changes one at a time: This means it only highlights one selected feature. In ExB, we follow this rule and keep all widgets consistent, since clicking on the map only gives you one result (even though pop-up methods display multiple).   In a sense, clicking on the pop-up resembles the behavior of using map select tools (since they both have buffer distance). Thus, the workaround you mentioned above is the solution here. Hope it clarifies a bit. ... View more

Hello @KatieDarcy, There might be various reasons why this happens. Sometimes when we select features on the map, especially using Select by point or Select by line, similar cases happen. Since a point or a line does not have any width, if you zoom to a certain extent, you might find the point is way off where you clicked. That's where buffer distance comes in handy. In some cases, we introduce a certain buffer so that the users could avoid the above issues. Another possible reason could be, there might be some layer or widget container (which is transparent) overlapping the map area, causing it not accessible.   It might be more clear if you could share the app for trouble-shooting.   Hope it helps, Tonghui ... View more

@MoniqueL_ - we will fix this issue in the upcoming release. However, there is not much of a workaround at this stage for AGOL users until the next release. ... View more

@RoseZhou2 Yes, it should be included in dev edition 1.5. ... View more

@BrittanyBurson - Oh and a workaround - currently, if you put the Filter widget (ExB) into a window, and when you close the window, the values got reset:   Note that this behavior might change in the future. ... View more

Hi @Anonymous User, It might be useful if you try the Refresh settings in the Select data doc:     ... View more

Hi @BrittanyBurson - this is the same issue as discussed in this post - Custom Filter widget to reset filter. It is something we haven't supported yet but a potential ENH we will take a look in the near future. Keep tuned.   Thanks, Tonghui ... View more

Hi @MoniqueL_  Thanks for bringing this up and sharing the app with us. It does look like a valid issue and we will take a look at it. ... View more

@asummerville @PutriKhalilahKamaluddin - In the dev1.4 version, if you have a special symbol or certain characters from other locales (e.g. JP, KO) inside the app title, there might be a problem with downloading the app. Could you please double-check and try a plain text title without any potential special symbols and see if it works? FYI, the issue I mentioned above has been fixed in dev 1.5.   Best, Tonghui ... View more