Couldn't two gnx be stored? - a short one visually acceptable for inside the documents that the external user will see, just with a refference to the actual gnx it refers to. Maybe just an index of the place that the real gnx has within the Leo document. - A second one, embedded in the Leo file, stored in a "list of gnx's", in a certain order that would be refered from the simple one. Just the position of the gnx's lists would need to be stored within the first one.
Well just a thought, maybe that would make things more complex.. But I liked the idea of extending the gnx's with big random number too. On Thu, Oct 23, 2014 at 10:40 PM, Edward K. Ream <edream...@gmail.com> wrote: > On Thu, Oct 23, 2014 at 12:59 PM, Todd Mars <tamn...@gmail.com> wrote: > > > Why not just append a big enough range random number to the end of the > > timestamp... > > Because gnx's appear in external files and people already think they > are visually intrusive. > > EKR > > -- > You received this message because you are subscribed to the Google Groups > "leo-editor" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to leo-editor+unsubscr...@googlegroups.com. > To post to this group, send email to leo-editor@googlegroups.com. > Visit this group at http://groups.google.com/group/leo-editor. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
