Hello Bret, So I’ve started to fool around with the One Zero and One Point files. After gathering some experience with the One Zeo files I’d propose a more flexible reading algorithm. I like these text files so much that I started to implement export functions to some of my modules (Vulcan, SaveMeMono, SaveMeMonoWide, etc.) and later on I also added import to some of them. I’ll surely will add it to a few more of my modules. But I implemented the code by mistake the proposed way: only ‘1’ and ‘0’ characters are considered (respectively as ‘true’ and ‘false’) for One Zero files. And it is a bless. Using my export functions all create the classic One Zero files: 1000100010001000 0010001000100101 01010101010101010101010101011111 But occasionally I also edit the text files manually. In this case it is immensely useful that I can add a space as delimiter. It’s easier to work with the file in a text editor. 1000 1000 1000 1000 0010 0010 0010 0101 0101 0101 0101 0101 0101 0101 0101 1111 01010111 01010100 01011101 01011111 Later I started to add some labels to my lines that I can see that I’m modifying the right line. KICK 1000100010001000 SNRE 0010001000100101 CHAT 01010101010101010101010101011111 In short: I would not encourage this extended format but I’d change the code to allow a more flexible usage. Regards, A. P.S.: One Point files are good as they are in my opinion.
