| Re: how do you
Nov 20 2007 on content weekalarm |
To use the script you should just have to do the following:
In Amarok:
Tools menu -> Script Manager
Select General -> weekalarm
Click Run
Click Configure
Select the days and times you want the alarm to turn on, optionally set other parameters such as playlist, snooze, etc.
Clicking save should result in the window closing and your settings being saved.
I just tried this on a new Gusty Kubuntu install and it worked for me. The only thing I can think of is that you're having trouble saving, make sure you can write to ~/.kde/share/apps/amarok/scripts-data
Also, try starting amarok from the commandline using amarokapp and see if you get any errors when you run the configuration.
Amarok needs to be running for the alarm work.
Hope this helps. |
|  | | Re: Wake up AND Slee
Sep 8 2007 on content weekalarm |
I've thought of this, but I haven't been able to think of a way to implement it without duplicating all of the time selection dialogs and adding quite a bit of complexity to the alarm function.
Is it something that you'd use for going to sleep at night, or for a nap? If it's mostly for napping I could make it work by adding a startup delay to the nap timer. |
| | | Re: Bug: wrong time!
Sep 3 2007 on content weekalarm |
I suspect this is caused by two instances of weekalarm running: one started by the KDE session manager, and one by amarok. This should be fixed in the 0.9.1 release. |
| | | Re: snooze
Jul 28 2006 on content weekalarm |
Setting snooze for 30 minutes means that when the alarm goes off, the "Snooze? Yes/No" dialog pops up, and if you select "Yes", the alarm will shut off for 30 minutes letting you grab a bit more sleep. It's for the type of people who set their alarms for before they really have to get up.
Cheers,
bfl |
| | | Re: custom playlists
May 12 2006 on content weekalarm |
Thanks for the tip, fixed this for 0.6.1. It worked previously, and then I broke it for 0.6. |
| | | Re: And in this corn
May 10 2006 on content weekalarm |
>Maybe you could have your script disable replaygain at the beginning and reenable at the end.
I'd rather not start disabling other scripts from within the script. If you would like to add it in yourself, the function you are looking for is
def fadeVol(self,start,step,stop)
Just add the line
system('dcop amarok script stopScript amarok_replaygain.py')
before the "for i in range" line, and add
system('dcop amarok script runScript amarok_replaygain.py')
after the "time.sleep" line.
> would it be possible to set the time it takes for the volume to increase or decrease
I added this to the 0.6 release, enjoy! |
| | | Re: close down @ tim
Feb 9 2006 on content weekalarm |
I think you can do this already. Head over to the volume tab and check "slowly decrease the volume and stop player".
Cheers. |
| | | Re: Python 2.4
Oct 15 2005 on content weekalarm |
I'm using python 2.4, and it works alright for me. Can you email some more info on the problems you're having? Thanks. |
| | | Re: snooze alarm
Sep 24 2005 on content weekalarm |
This should be fixed in 0.5.1. I resorted to using kdialog instead of a custom class; it's probably simpler and better that way anyhow. |
| | | Re: snooze alarm
Sep 10 2005 on content weekalarm |
I noticed this same thing. I think the problem is that the snooze popup dialog is a child of the script manager window, so if the script manager is in the foreground the snooze dialog will popup into the foreground, otherwise it stays minimised. If anyone knows how to get around this please let me know. I'm sure there's some Qt window flag that I can set: looks like I'll be doing some documentation browsing ;) |
| |
Search people
Current visitors
New users
Birthdays
Most active users
Back
|
|
