To support future features, I think I need to test for not only the first character but the second as well. If it is a double quote then we have a string that can have whitespace in it. This would have several important benefits. I could say:

@"Waiting For" - supporting categories with spaces
#"next Friday" - supporting due dates with spaces still no luck in finding a document with all the Outlook "shortcuts" for due dates btw
:"task bodies can have spaces already" - no known benefit that I can think of

-daddydave (October 20, 2010, 07:23 AM)

I think this is a good idea for other reasons too, though.  It makes it more transparent how things are parsed, and therefore easier for a user to create and/or read.  In other words, it just makes sense.
@ = category
# = date
: = body
" " = data
Once this is recognized as data, it is kinda like a comment - everything in between is ignored so any kind of character can be put in and utilized.  It also makes your data structures a little easier to handle as the space becomes your delimiter (unless it is between quotes) and the special character becomes your identifier.  Now that I think of it this way, programming it in Java (the only language I know with any semblance of depth) seems relatively easy to do.  Of course I bet you thought the same thing but with AutoIT when you started the project. ;D  I don't know what kind of string handling AutoIT has, but I know Java supports a rather rich set of string handling operations as does .Net languages, no doubt.  Perhaps one of those options would work better, unless you know C++ well already.

Yea.  Final release 1.0. is done(ish?)!  Okay, so none are as happy as you.   :P

Sorry the screencast results were never posted.  I lost my Hard Drive to a corruption sometime around the end of November and had to rebuild the PC and start over.  Not all is lost, though, and this final release lets me make a new screencast with what I learned from the original.  I will try to have it up tomorrow or the next day here.