Notices


Reply
Thread Tools
zlatko's Avatar
Posts: 861 | Thanked: 936 times | Joined on Feb 2010 @ Bulgaria
#301
For me callnotify IS working with PR1.2. It was working even with leaked RC1.2. Only problem is that I am not able to access settings via the GUI - when I click on it doesn't open. And that it always shows 5 unread SMS in status area.
 
Posts: 261 | Thanked: 73 times | Joined on Sep 2009
#302
thanks! hope it will come soon! i appreciate the work ;-)
 
Posts: 110 | Thanked: 38 times | Joined on Apr 2010
#303
Originally Posted by zlatko View Post
For me callnotify IS working with PR1.2. It was working even with leaked RC1.2. Only problem is that I am not able to access settings via the GUI - when I click on it doesn't open. And that it always shows 5 unread SMS in status area.
I am experiencing the same with PR 1.2.
 
Posts: 134 | Thanked: 42 times | Joined on Feb 2010
#304
Cant wait for the update. to get it working on 1.2.
Keep up the good work man.
 
omeriko9's Avatar
Posts: 385 | Thanked: 344 times | Joined on Jan 2010 @ Israel
#305
Originally Posted by mackan1 View Post
Cant wait for the update. to get it working on 1.2.
Keep up the good work man.
For anyone who wish to keep using CallNotify until I'll upload a fixed version (which I don't have yet), can edit the file /usr/lib/hildon-desktop/CallNotify.py as root, and change line 23 from:

self.path = "/home/user/.rtcom-eventlogger/el.db"
to

self.path = "/home/user/.rtcom-eventlogger/el-v1.db"
This will not solve the setting menu, only cause CallNotify to work with PR1.2.

Settings can be edited manually in /home/user/.config/CallNotify/conf.txt (y;y;y;5.0 means yes for visual, yes for vibration, yes for sound and notify every 5 minutes).

Last edited by omeriko9; 2010-05-28 at 16:31.
 

The Following 3 Users Say Thank You to omeriko9 For This Useful Post:
Posts: 388 | Thanked: 842 times | Joined on Sep 2009 @ Finland
#306
Originally Posted by omeriko9 View Post
If you will figure out, I would appreciate it if you can share the reason...
Having a call in the (shortcutd) panel applet code to change a static member variable of an included class (even if this was never executed...) caused the control panel to freeze
Oh well, didn't really need that anyway so I solved the problem by removing the offending code

Last edited by hqh; 2010-05-27 at 19:24.
 

The Following User Says Thank You to hqh For This Useful Post:
Posts: 53 | Thanked: 14 times | Joined on Mar 2010
#307
Originally Posted by omeriko9 View Post
For anyone who wish to keep using CallNotify until I'll upload a fixed version (which I don't have yet), can edit the file /usr/lib/hildon-desktop/CallNotify.py and change it from:



to



This will not solve the setting menu, only cause CallNotify to work with PR1.2.

Settings can be edited manually in /home/user/.config/CallNotify/conf.txt (y;y;y;5.0 means yes for visual, yes for vibration, yes for sound and notify every 5 minutes).
the modification above did not work for me... do i need to do anything after editing the file? i already tried to reboot...
 
omeriko9's Avatar
Posts: 385 | Thanked: 344 times | Joined on Jan 2010 @ Israel
#308
Originally Posted by n61adm View Post
the modification above did not work for me... do i need to do anything after editing the file? i already tried to reboot...
Reboot should work. You can also try this.

How did you edit the file? you should do it as root, otherwise you won't be able to save it after the change. After saving it, view the file to see if it reflects the change you've just made.
 
Posts: 15 | Thanked: 0 times | Joined on May 2010
#309
i am confused on how to EDIT these lines

can edit the file /usr/lib/hildon-desktop/CallNotify.py as root, and change line 23 from:
 
omeriko9's Avatar
Posts: 385 | Thanked: 344 times | Joined on Jan 2010 @ Israel
#310
Originally Posted by robertran88 View Post
i am confused on how to EDIT these lines

can edit the file /usr/lib/hildon-desktop/CallNotify.py as root, and change line 23 from:
You can edit the file without root, but you won't be able to save it, so gaining root is a necessity here.

VI is a very simple (or complicated, depends who you ask) text editor for linux. In order to enter the "edit" mode, you first need to press "i".
Otherwise, each letter will be interpreted as a command and led to crazy behavior of VI.

To exit "edit" mode, press ESC.
 
Reply


 
Forum Jump


All times are GMT. The time now is 12:31.