806
N.A.N.Y. 2011 / Re: NANY 2011 Pledge: LaserTask (until I can think of a better name)
« on: May 18, 2010, 09:20 AM »
For the name, I am now leaning strongly toward TaskDaddy. Any other suggestions are welcome.
I'm feeling much better about the command line parsing now, and I am rewriting it. There's a nice AutoIt include called _OptParse. The latest version of this is somewhat hard to find (if like me you search for these things in the AutoIt forums). I happened to click "Some of my scripts in Google Code" in eltorro's signature in the AutoIt3 forums. This version is about 2 years newer than the version he posted in that thread. It keeps the non-option arguments as well. Not everyone will use the command line options, but I wanted to get them right. I'm well on my way, thanks to _OptParse.
The meat of the Outlook processing is in wooltown's Outlook functions. They saved me a lot of work. There seems to be a bug in the error checking. It seems to always return an error even though the task gets created in Outlook. I may try to fix it, but for now, I've disabled that error check.
I'm feeling much better about the command line parsing now, and I am rewriting it. There's a nice AutoIt include called _OptParse. The latest version of this is somewhat hard to find (if like me you search for these things in the AutoIt forums). I happened to click "Some of my scripts in Google Code" in eltorro's signature in the AutoIt3 forums. This version is about 2 years newer than the version he posted in that thread. It keeps the non-option arguments as well. Not everyone will use the command line options, but I wanted to get them right. I'm well on my way, thanks to _OptParse.
The meat of the Outlook processing is in wooltown's Outlook functions. They saved me a lot of work. There seems to be a bug in the error checking. It seems to always return an error even though the task gets created in Outlook. I may try to fix it, but for now, I've disabled that error check.