> From: Toby Murray [mailto:toby.mur...@gmail.com]
> Subject: Re: [josm-dev] Is the "should upload" logic a little too eager?
>
> On Tue, Jan 1, 2013 at 8:18 AM, Greg Troxel wrote:
> >
> > On exit, JOSM offers to save data to disk when it's modified, and
On Tue, Jan 1, 2013 at 8:18 AM, Greg Troxel wrote:
>
> On exit, JOSM offers to save data to disk when it's modified, and this
> is of course totally fine. It also offers to upload, and I find this to
> be useful sometimes and sometimes troublesome, in two unrelated ways.
>
> * inspection of not-y
On Tue, 1 Jan 2013, Greg Troxel wrote:
A while ago, I made edits to an area (in JOSM, entirely normally, not
very large, 20 minutes worth of hand editing), and went to upload them.
My memory is fuzzy, but I think the upload had trouble, and when I went
to exit, I got the "should upload" prompt.
I have noticed a bit of weirdness related to this as well. There are
two main issues that I have seen in this dialog:
1) The logic to determine when a layer needs uploading seems to mark
it as requiring upload very frequently, but then if you cancel out of
the dialog and press the upload button
On exit, JOSM offers to save data to disk when it's modified, and this
is of course totally fine. It also offers to upload, and I find this to
be useful sometimes and sometimes troublesome, in two unrelated ways.
* inspection of not-yet-uploaded data case
Suppose one has a .osm file that's prop
