area info is only optional information during route creation. Compute is quite complex. For a few points (to around 500) it's not a problem, but display this info for huge area should be too complicated. And main problem is accuracy of this compute. When you define few points manually, you should see if area have correct shape (so no overlays) but when I'll compute are on some imported route, I'm not doing any computations to check area shape. So what about storing area info just in case, you create area manually in locus and you'll have enabled "Compute area" checkbox. In case you'll import route from some file or record by "Track record" feature, area value, will not be displayed ... hmm?
and gynta: I don't understand, you want to change this edit screen?
and gynta: I don't understand, you want to change this edit screen?