I am seeing the exact same behavior as Xiaoguang. I was pretty stoked when I saw the new RequireSelectionBeforeDrag property, but it doesn't seem to work as advertised. The selecting the border to move stuff is driving our customers nuts. It's not necessarily a problem to select the outline, but they just don't know that they have to do that to initiate a move. It's not a good user experience, so being able to do it the old way would be a big win for us.
Not sure if I'm doing something wrong, but here are the EditConfiguration properties I set up before any edits:
MainMapView.SketchEditor.EditConfiguration.AllowMove = true;
MainMapView.SketchEditor.EditConfiguration.AllowRotate = true;
MainMapView.SketchEditor.EditConfiguration.AllowVertexEditing = true;
MainMapView.SketchEditor.EditConfiguration.ResizeMode = SketchResizeMode.None;
MainMapView.SketchEditor.EditConfiguration.RequireSelectionBeforeDrag = false;
Even after setting those properties when I click on a graphic and drag the map pans. I still need to tap the line or polygon boundary to select it. Then I can click and drag the object. Setting the RequireSelectionBeforeDrag property does not seem to have any effect.
After I set those properties RequireSelectionBeforeDrag is false as it should be. The next thing I do is start an edit session with the selected graphic like this:
graphic.Geometry = await ApplicationManager.MainMapView.SketchEditor.StartAsync(editGeom, sketchCreationMode);
Immediately after my edit is done the RequireSelectionBeforeDrag property is true for some reason. Head scratcher there as I never explicitly set it to true. I would expect it to remain false until I tell it otherwise. I wonder if this is part of the reason it's not working as we expect it to.