AppLock v3.0: My views and conclusions

1. The UI fails to do anything or atleast fails to register what its doing.
This means: We run "applock-d" in terminal and start the UI from the app launcher.
In the GUI, when we click on a particular app, for example "contacts", the UI seems to do nothing but the command line shows that the UI made an attempt to add the selected application and its services to the database. But in reality, there is no effect whatsoever. The app is not locked. Tested this multiple times.

2. The UI does remove apps from the database
When clicking on unlock, even though the UI seems to do nothing again, the terminal shows that the application was removed and yes, in reality, it is removed. The UI crashes when trying to remove applications with dbus events like conversations for example but again, the application gets successfully removed. Confirmed this.

3. Applock still works like before, i.e you can add and remove apps using the CLI and this works. The only thing I was never able to get working was the "keypress events" i.e, the application should have locked contacts on pressing a key on the hardware keyboard, but it didnt. But most apps which are added to the database this way, adds a "lock" icon in the GUI and gets locked.

4. The GUI doesnt seem to behave according to what is happening in the background. Locking an application through the GUi is almost impossible though it does detect input from the user, as seen on the command line. But in reality, the app never gets locked this way.
Applications which are added using the CLI show a "lock" icon in the GUI but when unlocked through the GUI, fails to remove the "lock" icon beside the application. Tested and confirmed.

So well, these are my conclusions on v.3.0 and also the bugs I found. Hope I was able to point out the bugs clearly.

Keep up the work and keep it alive! This is definitely a good start as we reached till here. Thanks again! Patiently waiting for bug-fixes.
Cheers!