View Single Post
Posts: 121 | Thanked: 75 times | Joined on Oct 2009
#50
Originally Posted by kerneld View Post
Hadn't seen it.. Weird, though, that the "fix" is so simple and wasn't implemented by default. Oh well..

Anyway, probably more important than displaying end time for a call is the duration of said call (preferably in human-readable form.. 1:20 as opposed to 80seconds). Of course, if we could have all of it, start;end;duration, even better.

The talk says adding those triggers is relatively safe.. There doesn't seem to be any system-default triggers and running that batch command resets the list so unless some other app decides to overwrite them, it should be relatively safe putting that into your app's pre- or post-installation scripts.
Human readable format shouldn't be too much extra effort so would be ok. Although, I probably won't put the triggers as part of my install script, as I'd prefer to have that left somewhat separate to allow people to choose if they want to try it just in case it causes issues.
Maybe I could include a script that is easy to run that can be used to set up the triggers