Oh, it's not.  Actually v0.2 *should* be out by tonight if I can get all the bytes in the right place in the file.  I just haven't made much progress over the last week.  It hasn't been until today I finally figured out how to replace all the vbcrlf's in the main data string, because for some reason .Replace() wouldn't do it.   But, now, 1 week later, that I've got that working, like I said before, v0.2 *should be out tonight.  And Necro, your new file you made for me was very helpful.  Don't worry, that was not where the problems lay...

Yay, I was helpful.   

If you need anymore help, I dug up my text books for vb and would be willing to try to make a few needed routines.

I've been banned from the computer for the last (almost) week, so I haven't really worked on it at all lately.  Still, I feel like showing off what I have so far, so I have attached the installer for current v0.2.

Main Features:

• Pretty MDI layout  
• Opening of .8xp files
• Saving of .8xp files (NOTE, this is actually at about 95%.  You can save a file with this and reopen it with it, but because my file size routines, there's about 4 of them for every file, are not quite correct yet, any files you transfer will either time out the link, or give you an invalid file format error.  But if you still want to use it, you can, because once I come out with the next version, you can just open the file and re-save it with the new one and you will be good to go )
• Not much else yet...

Also, you have to type the commands with the exact case as shown on the calculator(eg. "If ", not "IF " or "if ") else it will just come out as those letters.  And if you want to type special charachters, well, TOO BAD! Either get over it, open a file with that symbol in it for copy-pasta, or wait until the version with a symbol palatte comes out.  

lol hmmm do you think you could eventually add auto token correcting and tab complete?


eg auto    IF becomes if when you press space after the token

eg  tab     iden !tab! identety(  


*geekboy1011 still cant spell lol

True, in TI-Graph link software, when you don't type commands exactly how they should, the software interprets them as 1 letter tokens (lower and upper case)

Why don't you have it ignore things inside quotation marks?

I would recommend ignoring things in quotation marks for now, and then after you get this program working go back and see if you can have it automatically substitute tokens for individual characters in strings.

As for determining whether something is a token or not (that's not inside quotes), what if you used "\" (or some other symbol) to specify that it's not a token (since it's less likely for someone to be using IF [=I*F] than If).  e.g. If IF=7 would be If \I\F=7?

For special characters, you could have something similar to what TI|BD uses on their forums (a box to the side where you can copy the special symbols and paste them in).