Opened 12 years ago

Closed 12 years ago

#2460 closed enhancement (fixed)

A few minor usability issues

Reported by: anonymous Owned by: team
Priority: minor Milestone:
Component: unspecified Version: latest
Keywords: GUI Usability Cc:


I have a few ideas for improvement:
I think it is not necessary to be asked if you want to download data from the server, that it will need one server request. This messages appears often if you download the osm data along your gps traces. Please only show this message if there is more than one query necessary.

If I upload something I want to know after the upload, if it was successful or not! I had a file created with API version 0.5 and opened it with josm latest version. I could not load it up, but there was no error message (than in the console). You cannot do anything anyway while uploading, so a message would not hurt, indeed, it would be very nice imo. :)

I you do not want to do this please point me to the files in the source code, maybe i can take a look at this i learn java in school and this should not be too hard to implement. I can compile josm, but did not find the files where i could implement the features mentions above.

Thanks in advance! :)

Attachments (0)

Change History (5)

comment:1 Changed 12 years ago by anonymous

If I cannot upload a changeset, I would like to know, why. This is at the moment not the case, the error message gets printed in the upload progress bar window and this popup disappears quickly. Better would be an error message you would have to click away.

Also meaningful error messages would certainly appreciated. At the moment one has to spy the connection with whireshark to find out, what was going wrong.
So please: Error number + answer from the server whats going wrong in the GUI.

comment:2 Changed 12 years ago by anonymous

... I would like to see what could cause this error (maybe copy the points from to josm, so if error number x occures, show what could cause x and list the points.) And also of course the answer from the server (maybe this is already enought, I don't know. But better bit too much information than too less.

comment:3 Changed 12 years ago by anonymous

And one more point I would like to add: I can right click on my gps trace and download the osm data arout the trace, which is a great feature. Now I would really like to download the gps traces of others also automatically, to compare the traces and so on. But of course theese should go into a seperate layer, so that I can tell my layer apart from the others.

Thanks :)

comment:4 Changed 12 years ago by anonymous

And one more thing: I would really like if JOSM would *not* steal the focus if I download big data areas. Every time a package transfer is finished JOSM steals the focus, so you ar unable to do something else while the area gets downloaded. I use Ubuntu 8.10 here, if that matters. With the openjdk from sun.

Apart from that the comment box in the upload window should have the focus if the window gets opened. So that you can type your comment in and press enter do start the upload. Also there should be imo a possibility to load up with no comment, because that is better than a comment that is crap like "asfasdgf". Maybe show a warning that the community would really like to see comments, but it should not be forced.

And every time I convert a .gpx layer to the data layer the window appears, that it is bad to upload not modified traces. Although I click on the checkbox, josm says this every time again.

comment:5 Changed 12 years ago by stoecker

Resolution: fixed
Status: newclosed

The "download one problem is fixed in r1658 as well as the "Dont show again" problem.

Downloading GPS traces to other layers should work also. You only need to create a new layer and change layer order accordingly.

Error handling has been improved a lot.

Modify Ticket

Change Properties
Set your email in Preferences
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.