Latest Contributions by CharlesMacleod

mody, in addition to what Uma says below, it is also possible to split your workflow into multiple steps where each step is within the context of a QueuedTask and, in between steps, u can show a modal UI to the user. The key is to "await" each step wrapped within a QueuedTask like so:   internal class Button1 : Button { protected async override void OnClick() { //step 1 - await it before proceeding to step 2 var ok = await QueuedTask.Run(() => { //do work return true; } //Back on the UI if (!ok) { MessageBox.Show("......"); return; //exit perhaps } //continue on to step 2 ok = await QueuedTask.Run(() => { .... //Back on the UI if (!ok) { MessageBox.Show("......"); //continue on to step 3 ok = await QueuedTask.Run(() => { ... //and so-on   The only caveat here is that each time that u return to the UI, there is an opportunity for other "processes/workflows" to use the QueuedTask in-between your steps so, ideally, u want to capture any state u need upfront (such as the layer u r examining into a local variable and so on) ... View more

"Regular" feature classes support schema locking and schema edits allowing (certain) changes to the schema to be made (restrictions apply - no pending edits, no edit session, etc, etc). Plugin datasources are readonly and the schema is fixed.  ... View more

The pattern looks something like this but I dont think it is going to give u the results you are hoping for: internal class MapTool1 : MapTool { private DelayedInvoker _invoker = new DelayedInvoker(50); ... protected async override void OnToolMouseMove(MapViewMouseEventArgs e){ //do something with the invoker _invoker.InvokeTask(() => { return QueuedTask.Run(() => { var mpt = MapView.Active.ClientToMap(e.ClientPoint); //Do something with the point }); Basically, just like a "QueuedTask.Run(() => { ........... })" you can wrap whatever u want to be invoked with the delay (50ms in this case) within the "_invoker.InvokeTask" lambda. So, in this case, if I am tracking the cursor position w/ the invoker I will be "processing" its position every 50ms (or whatever delay u specify) which will be quite jittery and so on. In the Pro SDK are a number of samples where we implement logic to cut down on unnecessary mouse movement - just search for "MouseMove" and you will see them - they are all using the same, basic pattern and are updating the graphics overlay in different ways. https://github.com/search?q=repo%3AEsri%2Farcgis-pro-sdk-community-samples%20mousemove&type=code I suggest using something built around the pattern they are using rather than the delayed invoker. Another way, that I have used from time to time, is this basic pattern: internal class SelectOnMove1 : MapTool { private Point _lastLocation; private int _deltaPixels = 0; protected override Task OnToolActivateAsync(bool active) { if (_deltaPixels == 0) //usually 3 pixels - use whatever number u want _deltaPixels = SelectionEnvironment.SelectionTolerance; protected async override void OnToolMouseMove(MapViewMouseEventArgs e) { //compare current cursor position to last (captured) position if (_lastLocation.X >= e.ClientPoint.X - _deltaPixels && _lastLocation.X <= e.ClientPoint.X + _deltaPixels && _lastLocation.Y >= e.ClientPoint.Y - _deltaPixels && _lastLocation.X <= e.ClientPoint.X + _deltaPixels) return;//within tolerance - ignore _lastLocation = e.ClientPoint; //we'll use this one //TODO - use the point   However, it is going to be v difficult to get truly smooth tracking and it will always be a little laggy/jittery. Your mileage will vary.     ... View more

the sdk will follow the behavior of the UI. Add field on a geopackage must not be supported. ... View more