Latest Contributions by KirkKuykendall

The Wait() method on the Task returned by QueuedTask.Run hangs when I try to use LayerFactory. If I use await , it works as expected.  Am I doing something wrong? This works: protected override async void OnClick ( ) {     await QueuedTask . Run ( ( ) = > {             LayerFactory . CreateGroupLayer ( MapView . Active . Map , 0 , "group layer" ) ;             Debug . Print ( "layer created" ) ;         } ) ;     Debug . Print ( "done" ) ; } ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ But this hangs: protected override void OnClick ( ) {     QueuedTask . Run ( ( ) = > {             LayerFactory . CreateGroupLayer ( MapView . Active . Map , 0 , "group layer" ) ;             Debug . Print ( "layer created" ) ;         } ) . Wait ( ) ;     Debug . Print ( "done" ) ; } ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ This works (suggesting LayerFactory is clogging the plumbing): protected override void OnClick ( ) {     QueuedTask . Run ( ( ) = > {         for ( int i = 0 ; i < 5 ; i ++ )         {             Debug . Print ( "Sleeping " + i ) ;             System . Threading . Thread . Sleep ( 1000 ) ;         }         Debug . Print ( "waking" ) ;     } ) . Wait ( ) ;     Debug . Print ( "done" ) ; } ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ... View more

I would expect the following code to essentially clone the top layer in the map.  It does create a new featurelayer that points to the Uri, but calling SetDefinition has no discernible effect. private void Test ( ) {     var def = MapView . Active . Map . Layers [ 0 ] . GetDefinition ( ) as CIMFeatureLayer ;     var conn = def . FeatureTable . DataConnection as CIMStandardDataConnection ;     var folder = conn . WorkspaceConnectionString . Split ( '=' ) [ 1 ] ;     if ( conn . WorkspaceFactory != WorkspaceFactory . Shapefile )         throw new Exception ( "test only works with shapefile layers" ) ;     var url = Path . Combine ( folder , conn . Dataset + ".shp" ) ;     var fLayer = LayerFactory . CreateFeatureLayer ( new Uri ( url ) , MapView . Active . Map , 1 ) ;     fLayer . SetName ( "my layer" ) ;     // name remains "my layer" Setdefinition has no discernible effect     fLayer . SetDefinition ( def ) ; } ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ... View more

I'm developing a WAB widget and testing it in a time-aware map.  The OOTB timeslider widget is also being used. I add a time-aware featurelayer to the map with ONDEMAND mode. The maxFeatures is 1000.  I would expect when query-limit-exceeded fires, that the subsequent firing of query-features-complete would show exactly 1000 features in the set.  This is not the case.  Here's the log as I increment the time slider, the first few times the features update as expected, until query-limit-exceeded fires: Sometime query-limit-exceeded will fire, even when the featset has fewer than 1000 features.  I suspect I'm misunderstanding how time-awareness works. var fLayer = FeatureLayer(url, {   mode: FeatureLayer.MODE_ONDEMAND,   outFields: ["mag"] }); var exceeded = false; fLayer.on("query-limit-exceeded",function(){     console.log("query-limit-exceeded");     exceeded = true; }); fLayer.on("update-start",function(){                    console.log("update-start")     exceeded = false; }); fLayer.on("query-features-complete",function(featset){     var cnt = featset.featureSet.features.length;     if(exceeded){         console.log("only showing first " + fLayer.maxRecordCount + " features, " + cnt);               }else{         console.log("retrieved ", cnt);                        } }); ... View more

I have a web app that uses the javascript Directions widget with configured to use my own network analysis service and configured to honor barriers in a featureservice. From the documentation, it's not clear to me if Navigator can be configured to use barriers in my featureservice.  If not, please consider adding this capability. Thanks! ... View more