Laurent Grenet

Hi Robert, I've just tested beta 7, and for me it's OK. I don't know if you are waiting for other changes to implement, but if no, this beta 7 is a very good candidate to become the next "official version"

For me, there are only two acceptable solutions : Either have two attributes, name and displayName Or only one (name) but accepting any character I prefer (from far !) the first one, that is more efficient and flexible, but the second could be acceptable, provided there is absolutely no forbidden character in the name. Among other choice elements between both, the one that is the easiest to implement should be preferred, mainly to avoid new bugs introduction... I let you to decide, Robert.

For me, there are only two acceptable solutions : Either have two attributes, name and displayName Or only one (name) but accepting any character I prefer (from far !) the first one, tat is more efficient and flexible, but the second could be acceptable, provided there is absolutely no forbidden character in the name. Among other choice elements between both, the one that is the easiest to implement should be preferred, mainly to avoid new bugs introduction... I let you to decide, Robert.

Hi Robert, FYI I did the test to create a "beta7" version, with latest source file (including your "bugfix: when clicking a map source in the list of available map sources directly get the map source; do not try to get the map source by its (display) name") but going back from your latest modif of mobac/src/main/java/mobac/mapsources/DefaultMapSourcesManager.java i order to remove automatic adding to displayName in case of "collision", and it works fine ! With this situation, all source have their...

OK, thanks for answer. Not a real problem, since there is an easy workaround... but this is more or less a bug in the Apache commons http client and its new constructor of URL / URI....

One more "strange" behaviour that comes with this beta version : It is no more feasible to have a "|" (pipe) character in a URL. There is an easy workaround : replace it by its hexa code : "%7C" But I don't understand why this character is no more accepted, since it is accepted in the address bar of Firefox, or in URL argument of curl command. PS : This character is in particular used in Google Maps URL when we customize which elements are displayed or not, thanks to the &apistyle=... parameter

For me YES, 10 times YES, 100 times YES !

Quite perfect like this. This gives a very good answer to the problem I mentioned above. We have now a clear and robust picture regarding the mechanism of default source in both Mobac and mapevaluator and clear distinction between internal name ("name") that has to be unique, and cannot contain characters that could generate problem in some cases on one hand, and on the other hand "visible" name ("displayName") that do not have to support any constraint. Thank you so much. PS: with the fix you did...