Latest Contributions by KristianEkenes

Yes. ... View more

In 4.0 beta1, there is no support to permit the camera to go below the surface. It's being discussed for future releases. Keep an eye out for more information related to this in the future. ... View more

Hi Josh, If a class is not documented in 4.0, it is not supported. You can certainly try to use the class, but it isn't recommended. DynamicLayer does not perform as expected. For that reason it is not documented in beta1. It will eventually be supported in a future beta release. Information related to the current state of the API is found it the API reference​. At the moment, we do not have a page dedicated to what we expect to develop and release in future betas since this changes often. As of now, you can expect nearly everything in the current 3.14 API to be included in the final 4.0 release (with the exception of deprecated classes like Geocoder). Regarding your last question, do we expect the code in 4.0beta1 to work against the final 4.0 release? That would certainly be ideal, but we cannot promise that all code structure will remain the same. That's one of the reasons we are releasing in beta - because the code base isn't completely stable yet. ... View more

Hi Gary, No, this is not supported at the moment. This is a concept we'll be discussing though and will let you know about future plans. ... View more

Hi Adam and Adam, The documentation on this is misleading and, in the cases you both brought up, contradictory. The reason for this is because the way these workflows are being designed has been changing and will continue to change as 4.0 progresses through multiple betas into the final product. The documentation reflects some of these changes over time, but isn't consistent with how things are now. We are updating it so that it will not be as confusing. featureLayer.graphicsCollection does not exist. The Migration page in the guide is wrong and will be updated soon. featureLayer.graphics exists, but as the original post mentions, doesn't actually do anything. This too will likely go away and accessing graphics on the view will change in the future. Stay tuned for documentation updates explaining this. There are a number of reasons featureLayer.graphics will no longer be used, the primary reason being that features are no longer rendered on the layer or the map; rather, they are rendered in the LayerView and View. This is a major difference between our 3.x and 4.x APIs, so keep a look out for updated documentation, blogs, etc that go into greater depth explaining these concepts and classes. In the interim you can access the graphics displayed in the view via the 'graphics-controller-create' event on the featureLayer. This is undocumented, but will be later. The event object has a graphicsController property, which is an object that has a graphicsCollection property. See this jsbin for an example of accessing the graphics using one of our existing samples: JS Bin - Collaborative JavaScript Debugging I hope this helps! ... View more

Yes. We plan on supporting the ability to switch the Map's spatial reference in 4.0. It's not there yet, but it will be explored. As of now, it looks like this will only be possible with Maps that have NO basemap. The SpatialReference of the map and all of the dynamic layers and FeatureLayers would reproject after changing the SpatialReference directly on the Map.spatialReference property. map.spatialReference = new SpatialReference( {wkid: 4326} );  //or some other spatial reference object ... View more