Internet security products are GREAT and everyone should use one - even if it's built in. However, as a software developer they can be a real hassle to tray and navigate the tricky waters to ensure your application is able to communicate via the Internet.  By far the largest number of user problems we've had with TripStalker have beena result of the users Internet Security product blocking it in one way or another.  I'm very happy to say that we have spent a great deal of time tweaking TripStalker so that it appropriatley triggers pop-ups from the various Internet Security products and informs the user if it is unable to connect out to the Internet. 

In addition, it seems that a lot of users would loose and gain their Internet connection quite frequently.  This was causing problems as the TripStalker would get confused if it was connected or not.  We have now modified TripStalker so that it is much more friendly and unintrusive during the loss of an Internet connection.  It just kind of quietly goes dorment waiting for the connection to be restored.  This should work better and drastically reduce the errors coming in through our automated error reporting.

Finally, we had a lot of errors being reported automatically (did not cause any adverse behavior to the end user) regarding the skin system.  This has been completely redone and should result in the TripStalker behaving much quicker than ever before.

These main items are what have occupied our days and nights.  We are glad to be closing in on them and will have a new build up soon.  Thanks to all of you and do visit our forums to chime in on your suggestions, thoughts, etc.!

 

Share this post: Email it! | bookmark it! | digg it! | reddit!