Latest Contributions by RhettZufelt

Just a stab as I don't have the setup to test it right now, but it looks like maybe an issue with terminating the parent tag before the child as I have fallen into so many times myself. Getting rid of the ending slash for the layer Subs might change it's behaviour. R_            <layer   type="dynamic" label ="Subs" visible="true" alpha="0.8"  url="http://engr_svr/ArcGIS/rest/services/Maps/TVECDATA/MapServer/">             <sublayer id="0" popupconfig="popups/PopUp_Subs.xml" />             <sublayer id="1" popupconfig="popups/PopUp_meters.xml" />           </layer>             <layer type="dynamic" label="Outages"  visible="true" alpha="0.8"  url="http://engr_svr/ArcGIS/rest/services/Maps/Outages/MapServer">             <sublayer id="1" popupconfig="popups/PopUp_Outages.xml" />             <sublayer id="2" popupconfig="popups/PopUp_Meters_Outs.xml" />            </layer> ... View more

Pretty easy to narrow down after you posted the changes to the code and I couldn't find it in my copy. Worked out better this way anyway.  I learn a lot more about the way these modules interact when I get to see the changes to the code rather than just an updated version. Thanks again for your time/help, Rhett ... View more

Robert, Thanks Robert, I made the changes you mentioned, and the DataTip is now following my Date format.  I also re-checked the zip file you posted earlier with the update and I do not see the changes in the files in the zip. Have cleared all my browser cache, etc. in case I was re-downloading a cached version and still don't see them.  Think maybe the zip file didn't get updated properly. Thanks again, Rhett ... View more

Thought I had changed all files, so tried again, but no change to result. So, thought maybe it was something I had done that was conflicting, so imported a brand new flexapp, added eTime widget, and have the same issues. So, thought maybe it was related to using the pre-release 3. Created a brand new 2.5 viewer project and brought in the eTime widget (even removed the normal Time widget module).  Same issue.  So, far, the only way I can get it to have the slider value year only is to make the change to the timeSliderSkin.mxml format string. Wonder if I'm missing something in my config xml or something (still using xml from previous post)?? R_ ... View more

Thanks again, and nice enhancement. However, the "datatip" (assuming that is the text box on the slider window itself) does now honor my xml settings.  However, if I grab the slider and move it to a position manually, the pop-up info/tip still has Jan 1, YYYY at 12:00 AM. If I make the mod on the slider skin, it will then just show the year itself and doesn't "create" the day/time info (see attached photos). R_ ... View more

That did the trick. Thanks again for your timely solution. Also, I modified this line in the TimeSliderSkin.mxml         <mx:DateFormatter id="dateFormatter" formatString="MMM D, YYYY at L:NN A"/> to         <mx:DateFormatter id="dateFormatter" formatString="YYYY"/> Now it no longer makes up a day and time when moving the slider manually.  Only shows the year as in the time field. I tried to figure out how to use an If format == "YYYY" then formatString="YYYY", that way, it would be more robust to other layers/maps.  However, for this map, the only time enabled layers are by 4 digit year only, so a mod to the skin.mxml works fine. Thanks again, Rhett ... View more

Unfortunatly,  my services are not available publicly. Here is what my polygons look like: [ATTACH=CONFIG]13782[/ATTACH] I have two attribute columns.  One is a text column of length 20 and the other is a short column length 2.  Both have a 4 digit year between 2010 and 2015 and each polygon only has one year assigned.  The idea is to have only the polygons with the respective year to display as you move the slider.  I have tried using both of these columns and have the issues.  With the Time slider, I got it to work using the text column as the time field.  Well, it "works" with the eTime also, just gives me the two steps per interval issue. I am using the un-compiled version so can do any testing needed.  Right now, I am actually using the pre-release3, but, to make sure it wasn't related to that, I have also set it up in the 2.5 version and have the same results. Here are the rest attributes for my service (minus the symbology info to reduce size): Layer: TA (ID: 0) Display Field: Year_of_Trans Type: Feature Layer Geometry Type: esriGeometryPolygon Description: Definition Expression: Copyright Text: Min. Scale: 0 Max. Scale: 0 Default Visibility: True Extent: XMin: 558473.4375 YMin: 113834.0086 XMax: 594972.687500002 YMax: 154573.8906 Spatial Reference: 32149 Has Attachments: False HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText Time Info: Start Time Field: Year_of_Trans End Time Field: N/A Track ID Field: N/A Time Extent: [2010/01/01 08:00:00 UTC, 2015/01/01 08:00:00 UTC] Time Zone: Pacific Standard Time    Respects Daylight Saving: True Time Interval: 1 (esriTimeUnitsYears) Export Options: Use Time: True Time Data Cumulative: False Time Offset: 0 Fields: OBJECTID (Type: esriFieldTypeOID, Alias: OBJECTID) Shape (Type: esriFieldTypeGeometry, Alias: Shape) Shape_Length (Type: esriFieldTypeDouble, Alias: Shape_Length) Shape_Area (Type: esriFieldTypeDouble, Alias: Shape_Area) Year_of_Trans (Type: esriFieldTypeString, Alias: Year_of_Trans, Length: 20 ) time2 (Type: esriFieldTypeSmallInteger, Alias: time2) Type ID Field: N/A Thanks again for looking into this Robert,  let me know if I can test anything or answer any other questions that may help, Rhett ... View more

Thanks for the info.  Still can't figure out what is going on here. Here is my timewidget_config: <?xml version="1.0" ?> <configuration label="2015 Visiontest">     <dateformat>YYYY</dateformat>     <loop>true</loop>     <singlethumbastimeinstant>true</singlethumbastimeinstant>     <thumbcount>1</thumbcount>     <thumbmovingrate>1500</thumbmovingrate>     <timeextent setfromlayer="2015 Visiontest"/>     <timestops>         <timestopsinterval>1</timestopsinterval>         <timestopsunits>years</timestopsunits>     </timestops> </configuration> and here is the eTime widget_config: <configuration>       <layers>   <layer label="Year Of Transition" name="2015 Visiontest">       <dateformat>YYYY</dateformat>       <loop>true</loop>       <singlethumbastimeinstant>true</singlethumbastimeinstant>       <thumbcount>1</thumbcount>       <thumbmovingrate>1500</thumbmovingrate>       <timeextent setfromlayer="2015 Visiontest"/>       <timestops>           <timestopsinterval>1</timestopsinterval>           <timestopsunits>years</timestopsunits>       </timestops>   </layer>     </layers> </configuration> Seems like they should be working "the same", but they are not.  The Time widget is giving me ONE interval per year (each time I move the slider one "click", it increments it one year).  With this same config, the eTime widget is giving me TWO intervals per year (have to move the slider two "clicks" in order to increment one year).  Both are using the same time enabled service, yet behave differently. Do you see anything that I'm missing here? Thanks again, Rhett ... View more

Bump, and more on this. It appears as if this is not an eTime widget issue, but a Time widget issue in general. Does not matter if I load the eTime or Time widget, it is still appears to be "creating" time sequence data on it's own. I am used to server changing config files on it's own, but can't figure out where these extra time "intervals" are coming from, but they don't appear in ArcMap. R_ guess it is an eTime widget issue afterall.  I can configure the Time widget to increment by year with only one stop per year.  However, if you drag the slider, it is still putting time/date info in there from somewhere. However, the eTime widget, no matter how I try to configure it, seems to automatically break each interval into "two" stops. ... View more

Bump, and more on this. It appears as if this is not an eTime widget issue, but a Time widget issue in general. Does not matter if I load the eTime or Time widget, it is still appears to be "creating" time sequence data on it's own. I am used to server changing config files on it's own, but can't figure out where these extra time "intervals" are coming from, but they don't appear in ArcMap. R_ ... View more

Is there a way to have it display ALL of the time features after the time sequence has finished? I don't want it to be cumulative, and only want to see the polygons by year.  However, after it "finishes" the time sequence, would like to display ALL of the features. Thanks for any help, R_ ... View more

Hi Robert, I have downloaded your latest source code and replaced all the contents in my InfoTemplates folder (other than the config files).  then, re-built project, and even did a clean. However, I am still getting the missing title on second click (once layer switched). To simplify, I stripped all the layers from my map except two, loaded as type=feature coming from two separate services, and with different attribute item names. I can click on as many features in one layer as I want, and it works fine.  Then, I can click on as many features from the "second" layer as I want and it works fine.  HOWEVER, when I switch layers a second time, it goes right back into the "have to click twice" to get the label issue.  From this point on, every time I click on a feature from the "other" layer (other meaning other than the one I just clicked), it will not show the title unless I click the feature a second time. Once I do click on that layers item a second time, it will keep working correctly as long as I keep clicking that layer only.  Loses it again on switch. If I do a refresh, it starts over letting me switch between layers ONCE. Work around for now is to not have a title block, and put the titlefield as the first <fields> item.  However, sure like the bold title up there (when it works). Thanks agian for the help, Rhett ... View more

Already tried that, but didn't work. Thought maybe it was related to the warning about "Duplicate Variable definition", but if I hard code that, it still takes it. I.e.,     If I modify it to this: var title:String = "Testing"; map.infoWindow.label = title;. Then it picks it up every time and always says "Testing" for my label no matter how much switching between services I do. So, I then did this: var title:String = titleField; map.infoWindow.label = title; So, it should now put the <titlefiled> field name up there instead of the value.  From this, I can tell that it is using the <titlefield> from the last config file the first time you click on a feature using a different config file. Example, I have a waste site point layer <titlefield> = "sitecode" I have a waste site line layer <titlefield> = "sitecode" I have a building layer <titlefield>="name" with the modification I mentioned above, if I click on a wastesite point feature, the popup label is "sitecode", if I then click a building feature, the popup label says "sitecode" (wrong), if I click it a second time, it will now say "name" (right).  Then, click on any waste site, and the label is "name"(wrong),  click again and it says "sitecode"(right). Of course, I can click between the wastsite lines and points and it works as both have the "SITECODE" field.  So, it seems to be pulling the <titlefield> from the last layer config file, BUT is extracting the data for that field from the correct (current) layer. So, the reason it was not "mis behaving" when I cliked on different sub-layers is that both of them have a "sitecode" field so it could extract the value.  It is when it tries to get data from a field that doesn't exist (because it is using the <titlefield> from a differnent layer, and that field does not exist in this data set (buildings does not have a "sitecode" field)) that it returns a blank. Any ideas on how to make it read the titlefield from the correct config file (instead of from memory or wherever it gets it) the "first" time I click a feature? Thanks again, Rhett Little more on this.  Just noticed that I can click on many features in a layer and it keeps working.  The first time I click a feature from a different layer  it works correctly also.  Any more clicks after that is when it starts misbehaving as above and keeps misbehaving until I do a reload of the page <cntr> <F5>.  So, it lets me switch between layers once only. ... View more