Hi,
First off, I'd like to thank Ron for tweaking say.dll. I can now use the command succesfully! A real relief from the strange method I had to use before...
Now for the meat...
These suggestions are once again for say.dll
1. Allow .direct. testing of say.dll from the dialog box, using a "test" button or similar.
2. Increase the size of the text buffer, to allow longer messages (Because I'm greedy);^)
Maybe a user selectable buffer size, if some don't want whatever resource drag that doing so might cause...(Don't even know if it would make any difference, but just in case)


Reply With Quote
