Re: [josm-dev] Layer specific history

Option 1) is the way, the undo/redo stack works at the moment, when you have multiple data layers. I like this, as it is the simplest and most conventional. Option 2) isn't too bad either. Paul ___ josm-dev mailing list josm-dev@openstreetmap.org

Re: [josm-dev] IPv6 problems

On Wed, 30 Dec 2015, Greg Troxel wrote: I have been running JOSM for a long time, on a Mac, currently at OSX 10.7. I have functional IPv6, but my tunnel is from OCCAID, and occasionally some places are unreachable - currently api.openstreetmap.org is one of them. josm starts up and proclaims:

Re: [josm-dev] How to ask for confirmation at layer deletion or exit?

Hi Vincent, The idea behind requiresSomeAction() was to display a message like "use the layer context menu to store modified data" to tell the user that there is more than "save session", "delete/exit now", and "cancel". Kind of an "other ways to handle modified data" information in the

Re: [josm-dev] How to ask for confirmation at layer deletion or exit?

A ticket with a patch? :) 2015-12-31 16:47 GMT+01:00 Holger Mappt : > Hi Vincent, > > The idea behind requiresSomeAction() was to display a message like "use > the layer context menu to store modified data" to tell the user that there > is more than "save session",

Re: [josm-dev] IPv6 problems

On Thu, Dec 31, 2015 at 02:44:59PM +0100, Dirk Stöcker wrote: > JOSM and Java do not try different protocols. If you (and the remote > server) have IPv6 it uses IPv6, if not IPv4. > > It seems you have a broken IPv6 connection which sometimes works and > sometimes not. You should fix it. t I

Re: [josm-dev] IPv6 problems

On Thu, 31 Dec 2015, Florian Lohoff wrote: I disagree on that. The fallback to v4 should be per CONNECTION and not per application restart. The RFCs are pretty clear on this and further behaviour improvements on intermitted ipv6 connectivity. We had the same discussion already here. Most of

Re: [josm-dev] IPv6 problems

On Thu, 31 Dec 2015, Greg Troxel wrote: I should clarify: My IPv6 setup is working fine. The problem is that my upstream ISP has routes to most parts of the v6 world but is missing a few, I'm guessing due to a peering dispute. This is the same sort of thing that can happen in v4, although I

Re: [josm-dev] IPv6 problems

On Thu, Dec 31, 2015 at 11:09:24PM +0100, Dirk Stöcker wrote: > >JOSM is a pain in the ass concerning ipv6. I typically roam with my > >notebook between dualstack and ipv4 only locations with suspend/resume > >and most of the time i need to save session restart josm etc. > >Its not even

Re: [josm-dev] IPv6 problems

I should clarify: My IPv6 setup is working fine. The problem is that my upstream ISP has routes to most parts of the v6 world but is missing a few, I'm guessing due to a peering dispute. This is the same sort of thing that can happen in v4, although I think it is less common. So this is a