POST
|
It seems that one of two things is happening here... Map topology may be enabled and thus maintaining coincidence of these points when moving one of them. If this is the case it can be easily fixed by selecting "No Topology" from the drop down on the Edit tab's "Manage Edits" group. This choice will be stored in the project and moving will independently move points again. These two layers are referencing the same dataset so they are aliasing one another, e.g. you don't actually have two points in the database but you have two layers rendering the same point with different symbology on the map. You can detect this case by examining the "Source" page of the layers' property sheets. If this is the case you can't independently move these points while the layers are referencing the same feature in the database.The correct course of action depends on what you are trying to model (are these points supposed to be independent etc).
... View more
07-11-2018
09:48 AM
|
1
|
2
|
2100
|
POST
|
A couple suggestions... You should call Dispose() on your cursor after using it the canonical way of doing this is with the using block. You should verify some rows were found (oidSet isn't empty) before attempting to make an edit. You should verify at least one of these rows doesn't already have this value for "SUBDNAME" set before attempting to make an edit (non-edits may still be reported as 'failed' (well they certainly didn't 'succeed'). ApplyAsync on the inspector creates its own edit operation, which is setup to report a failed edit through a modal dialog. If you want more control over the operation you can create your own... var op = new EditOperation();
// op.ShowModalMessageAfterFailure = false; // This shouldn't be necessary as its the default (but not through inspector.ApplyAsync()
op.Modify(insp);
bool succeeded = op.Execute(); You shouldn't call MessageBox.Show from the background thread, UI should be reported on the UI thread. This is overly convoluted and non-idiomatic. return 0; is preferred. return await Task.FromResult(0);
... View more
06-29-2018
07:45 AM
|
0
|
0
|
1851
|
POST
|
This has been fixed in Pro 2.2, sorry for the inconvenience. Thanks
... View more
05-30-2018
09:48 AM
|
0
|
0
|
822
|
IDEA
|
Just to clarify, there is not a Jerry Garcia Easter Egg in Pro.
... View more
05-29-2018
01:41 PM
|
1
|
1
|
1129
|
POST
|
Thank you for pointing this out, this has been fixed (for the next release of Pro).
... View more
01-17-2017
09:57 AM
|
1
|
1
|
483
|