Changes reads Merge writes In order to make safe a potentially "dangerous" operation, the write is done in two steps so the user can confirm what is going to be written (or have a chance to check if changes are the ones expected or not and abort without modifying the code).
It's functionally correct but the UI can be soooo much better with some tuning. I'll post something that might help us on this subject On Jan 2, 2014, at 9:04 PM, Hilaire Fernandes <[email protected]> wrote: > Le 02/01/2014 20:37, Marcus Denker a écrit : >> I always use “merge”. “Changes” will e.g. show all the changes towards >> everything changed >> in between, too. > > > For me this is weird, I can't understand the logic. > Merge: shows you the changes then let your merge > Change: shows some other sort of changes I don't understand. > > > -- > Dr. Geo http://drgeo.eu > >
