[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
StylusLock versus TouchLockPro

This is a reply on this post in Stylus(BattC)lock (v1.7)

Actually, TouchLockAction deletes already all other language files, when started the first time. So essentially, only a the following disk space is left: TouchLockPro: 127 KB, TouchLockAction, 334 KB. You can even store it on the memory card and not on internal memory, if you still find it too much. And as said TocuhLockPro is small in memory (38 KB). And also CPU usage is still 0.0%. If you do not need TouchLockAction , you can remove it, after configuring your settings.

You can also export the zuinige rijder registry keys and import them again, if you do not like the TouchLockAction program. But the registry keys will not be removed at deinstallation, so the settings will survive a new version.

I am always open for improvements. I know I cannot honor all requests, because I am limited too in my time. My approach is that TouchLockPo should be working out-of-the-box as much as possible (it detects the availability of sensors and uses them when they are available). Of course, people have different preferences, so the only way to serve them, is giving the possibility to tweak it to their needs. So this is a positive thing, but for a novice the configuration options look enormous. But maybe an advanced/expert Settings screens and novice Setting screens would help? I started with a QuickStart description, I providing help in the jungle of options and features. And if people can help in providing better descriptions (English is not my native language and I am more a technical writer than maybe providing clear and conscise descriptions), just PM me with better descriptions.

That is why I try to let it work as much as out-of-the-box with the default options.

No, StylusLock did not have the light sensor yet. I use the light sensor only for unlocking, not for locking.

Strange, it should work. I will try it out. However, on the eish list is already Make setting like Vibrate for the number of Beeps, avoids confusion and gives more flexibility.

I think you misunderstood, you must configure HTCLockAPI = 1, when you do not want the task manager clickable, the TouchPanel locking leaves the scrolling area touchable, but in general that does not harm.

Yes, I made a separate TouchLockAction program, so it would only be in memory when started. And I could program it in C#, so it was easier to program. Still I did make it compatible with .NET Compact Framework 2.0, so you are not forced to install 3.5 (like other programs often require).

Strange, because I do nothing with the standard clock/battery indicator, I just overlay it with the BattClock. So this is not the fault of TouchLockPro, so I am :confused:

As said, I do not feel attacked or offenced, TouchLockPo has become what it is now, by all suggestions from people interested in TouchLockPro. I try to pick out the good idea's, keeping in mind the Design principles, to keep TouchLockPro lean and mean, and with no negative effect on battery life. .And yes, I think, despite the numerous options, 38Kb in memory is peanuts, and still having advanced features.

All of the items you mention can already be done by TouchLockPro and even more except for + beep as well as vibrate (and or or) is already on the wish list.

I think I cannot make one version which fits for all. The only thing I can do make it work as much as out-of-the-box for the most common used locking needs. I also need to take into account the different phone types, e.g. on some phone there is no Stylus sensor or other sensors.

Can you be more specific what you mean by the light sensor and behaviour profile, because I did not understand that one :confused: