OpenCPN Routes Problem

[nohal]

Fabbian,
of course this bug will be fixed and if nobody will be faster it will probably be me who fixes it as I wrote this piece of code anyway...
The fix is not very complicated be it whatever, complicated is my current geographic position and size of a computer that fits in my backpack actually
But I would like to do it the right way - and think that regenerating the guids the way you suggest is a bit too aggressive approach. Would a dialog asking you what you want to do if there's a conflict in guids at import time (replace existing/regenerate guids/cancel) satisfy your needs or is there some other case you have on mind that would not be possible with it?
Why don't I want to change guid that often? Because I'm not convinced that moving a waypoint always makes it a completely new waypoint and I don't think changing a letter in a route name makes it a different route.
Right now it would really not be a big deal, but what I have on my mind for the future is making it possible for the plug-ins that need own data and maybe even online services to interact with OpenCPN and thus don't want to throw away the id's when it's not necessary.

Comments of course welcome

Pavel