> Your Leo id is part of every so-called gnx, the unique, immutable > identifier of each node. This is required to make clones work > reliably. Time stamps are not enough: two separate people, in two > separate places, might make a node with the same time stamp. Thus, > gnx's must consist of a time component and a "space" (id) component.
OK, now I understand. How about this shortened version for tkGui.py and qtGui.py: "Leo uses this id internally [or "behind the scenes"?] to uniquely identify nodes and maintain the overall data integrity of .leo files." On Aug 1, 4:21 am, "Edward K. Ream" <[email protected]> wrote: > On Sat, Jul 31, 2010 at 6:21 PM, taa <[email protected]> wrote: > >> - The dialogs that ask for the Leo ID now tells why Leo needs it. > > > I think this refers to this new line in tkGui.py and qtGui.py that > > says: > > >>Leo uses this id to uniquely identify nodes. > > > OK, that's more than I knew before, and I have no objection to putting > > in the ID, but why does Leo need to "uniquely identify nodes"? To put > > it another way, what would "break" if there was no Leo ID? > > Your Leo id is part of every so-called gnx, the unique, immutable > identifier of each node. This is required to make clones work > reliably. Time stamps are not enough: two separate people, in two > separate places, might make a node with the same time stamp. Thus, > gnx's must consist of a time component and a "space" (id) component. > > Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
