New Build: v0.6.7

Ok, thanks for the clarification. I definitely didn't know that.

It's odd that the system works like that though. There should be a way to hook/unhook by code. But that's a Google/Android issue, I know, I'm just saying.

Nazgulled Wrote:Still, can't you hook to those events/triggers only when the options are enabled? And unhook them when the options are not select? Wouldn't that work?

The hooks are defined in the xml file and registered to the system that way. You can't just unhook them... it is a static way right now.

But why bother? It is sitting there and is doing nothing. It wont cost you any of your battery life. And if it bothers you that much grab yourself the source and compile it without the hook.

Cause I'm picky and I don't like things that shouldn't be there, that's all.

I could compile it like that, but in case I need to enable the option, I need to compile it again. That's why I wondered about hooking/unhooking by code. Apparently it's not possible and I understand that.

Oh, boy.