Quote:
Originally Posted by jcragg
May not be the best, but it works, and it does not mess up any of my other programs.
|
well you could be right. the 'other threaded sms apps' might not be easy as this one, but it's not for novice user anyway (for installation). But in terms of usability, the txtman didn't work for me, just to give you a few examples;
1. threaded message won't work if txtman app is not running. so sometimes it goes to inbox, sometimes it goes to txtman. no consistency
2. even if I select option to keep a copy of sms in pocket outlook, the function doesn't seems to work, so pt #1 remains
3. a few instance the threaded message file/database corrupts and txtman won't run as a result. Solution from txtman's developer? delete the threaded message db/file! so much about its robustness. so beware if you are using this as your primary text'ing application.
4. when message is being sent out, it appears to make use of html/IE to send out. It doesn't sound to me that the app is making use of native api to send out, and to me, just creating another pt of failure. Plus, the IE status bar appearing each time I send out a message is pure ugly. I don't like it.
5. why can't developer make use of native code instead of using .NET CF??