I’m sure I understand what you mean by trial and eror method. Can you share more details about what exactly you are trying to accomplish?
Is there a typo in that? Did you leave out the word "not"?
ASSUMING you had a typo, the "Trial and error method" means:
Run the acreage.
Move a coordinate.
Run the acreage.
Move a coordinate.
Repeat, until it's pretty close. Set corner, and go home.
IF you try this, and the coords are Points 1, 2, 3.
It needs to be .45 ac. Hinge is 1. 2 is a fixed point. 3 has to be adjusted, to make it 0.45 ac, along a certain bearing from 2.
You guess at the location of three, at 110' from 2. @ bearing of S 10°05'15"E from 2.
Run acreage. Too big. Move it to be at 109.5. Still too big. (Now, you can see how much the acreage changes, in 1/2 a foot)
Move it to be at 109' That's real close, close enough. Run acreage to confirm, and we are done.
To MOVE pt 3, you have to DELETE it, and re make it, with simple cogo. To recompute the area, you have to EDIT and place pt 3 back in the sequence, because when you deleted it, it was also deleted from the acreage sequence.
This is cumbersome. IF we could simply OVERWRITE that coord, (With a warning) and it did not DELETE it from the Area point sequence it would be easier.
Move coord, and re run acreage. Move coord and re run acreage.
Secondary issue:
I'd also like it if EVERY time you overwrote a coord, in this manner, that it created a file, called over written coords.
So, pt 3 was changed 3 times. Each time, it simply shows a date, and time, and old and new coord.
This would not be needed for rotate and translate, but for simple cogo overwritten points. This way, you could look at that file, if you goofed it, and find an accidentally overwritten coord. and restore an iteration of the coord.
Nate