Image 01
profile-image

djarvie

David Jarvie Aberdeen, United Kingdom
Utilities

KAlarm

Utilities Apr 02 2012
Score 80%
80 Likes
20 Dislikes
KAlarm

Utilities 72 comments

Score 80%
80 Likes
20 Dislikes
Apr 02 2012
I think that you got further than me in setting up the N810 for KDE development, so you seem better placed than me to find out the answer to your question. I look forward to the results! - Sep 23 2011
KAlarm's main window doesn't specify its position - it just goes wherever the window manager puts it. Only the alarm windows are specially positioned, depending on your preferences. So I don't really understand your comment. - Sep 02 2011
There is no plasmoid currently, and there probably won't be until KAlarm has been converted to use Akonadi - this will make it much easier for other applications to access alarm data. The Akonadi conversion should hopefully be done for KDE 4.6 (early next year). After that, it will depend on somebody deciding to create the plasmoid. - Jun 11 2010
Just to be sure that I understand correctly, are you asking for an option to use KNotify to display alarms, instead of displaying an alarm message window?

If so, would you prefer it to be a global option for KAlarm applying to all alarms, or should it be selectable for individual alarms? - Apr 03 2010
I don't think it is essential to have $KDEHOME defined - it may just default to ~/.kde .

The error creating menus is because you installed into /usr/local instead of into the KDE installation directory (presumably /usr). Configuration files (such as the menu definition) are still being taken from the KDE installation instead of from /usr/local. If you install into some other directory such as /usr/local, you need at the very least to have /usr/local as the first entry in $KDEDIRS when the KDE session starts. If you want things to work properly, I'd definitely recommend installing into the normal KDE directory unless you really know what you're doing. - Jun 23 2008
It certainly should be backwards compatible. Perhaps for some reason the new version isn't looking for an alarm calendar file in the same location as the old version used. Are you running with the same KDE config directory ($KDEHOME, which is usually ~/.kde)? I wonder whether installing it in /usr/local instead of /usr may have made it look in the wrong place.

You can check the calendar file's location by displaying the resources view (in the menu, View -> Show Resources). Hover the cursor over the active calendar entry and it will display its file location. Check whether this is indeed the same file as was used by the previous version of KAlarm, which would usually be ~/.kde/share/apps/kalarm/calendar.ics . - Jun 23 2008
Do you have the Qt 3 development package (which contains header files) installed? It's probably called qt-devel or qt3-dev or something along those lines. - Jan 02 2007
Great! I'll put a link on the KAlarm website once you update the address here. - Jul 25 2006
Is the package a specifically Italian one, or is it a standard Slackware package for all languages? If the latter, I'll put a link to it on the KAlarm home page. - May 23 2006
KCron is simply a front end to cron, so its abilities are the same as cron's. See 'man cron' and 'man 5 crontab'. There is a difference in the ability to schedule repetitions - KAlarm can do things like every 1st Monday of the month, but cron can probably handle more complex timed repetitions than KAlarm. KCron can only invoke external commands - it doesn't have KAlarm's built-in message display, sound playing or email transmission (and KAlarm can also execute external commands). Cron also doesn't have reminder, cancel-if-late, etc. KCron can schedule commands to execute while you are logged off, while KAlarm requires you to be logged in when an alarm is triggered.

That's a summary of the differences. Use whichever is best for your particular needs. - Mar 19 2006
I've been thinking about this, and I tend to agree that WHAT is to be done is the first thing, followed by WHEN. Your point about the reminder being related to the time is, I think, a valid one. The reason it is in the action section is that I have kept all controls which are common to all types of action in the same position in the tabs. Since reminder only applies to message and file actions, it has been put in the action section. But perhaps this isn't really logical from a user's point of view.

I'll try putting it to the KDE usability list, and see what comes of that. - Mar 09 2006
The time entry spin boxes with two pairs of spin buttons ARE implemented using 2 separate spin boxes, with all but the arrows hidden in one of them.

Your comments about the alarm dialog layout are interesting. I'll try out putting the time at the top. The alarm type with associated configuration is already effectively in tabs (When you select a different alarm type, a different set of data entry widgets shows.) But I can't see an obvious way to reduce the number of widgets on show without making them more inaccessible, although I agree that simplification of the dialog would be desirable. I don't really understand what you're proposing in this respect. Can you please explain in more detail? - Jan 23 2006
Now fixed in version 1.3.7. - Jan 23 2006
I've had other reports of this problem from people running SUSE 10. I think that what is wrong is that SUSE have compiled KAlarm to not use the aRts sound server (i.e. specifying the WITHOUT_ARTS compile option). In that case, I'm afraid that the only solution is either to find a package which has been compiled to use aRts, or to recompile KAlarm from source. It might be a good idea to report this problem to SUSE. - Dec 29 2005
That is a mistake - thanks for pointing it out. It should get installed under the KDE installation directory, in share/apps/kalarm. I'll fix it for the next release. - Dec 19 2005
I assume that you are running KAlarm version 1.3 or higher. When you select Sound in the Edit Alarm dialog and then select File and if necessary click the sound file selection icon, you should see a dialog entitled "Sound File - KAlarm". There is a Repeat checkbox in that dialog. - Nov 23 2005
It still does have a repeat sound option, accessible when you click the sound file selection icon. - Nov 23 2005
Cron doesn't provide the flexibility required for recurrences, so it simply isn't practical.

KAlarm isn't designed to take the place of cron. So if you want to schedule tasks when you aren't logged in, use cron instead. - Aug 26 2005
Version 1.3.1 now includes an option to log command alarm output to a file (in append mode). You choose the log file individually for each command alarm. KAlarm doesn't provide any facility to read log files - you just use normal utilities to read it.

I hope this is useful. - Jun 03 2005
Sorry, I misunderstood what you said. But with a Snooze button, wouldn't you need to be able to select how long to snooze for? If so, it's really no different from using the Defer button along with selecting a value in "Defer for time interval". - May 05 2005
Doesn't the Defer button do what you want? - May 03 2005
This is a problem several people have reported with SUSE 9.1 and 9.2. The SUSE arts package seems to be modified from the standard KDE source - these missing 'functions' are defined as macros in KDE, so would never produce these error messages. I hope SUSE will fix this sometime. - May 03 2005
This has been fixed in version 1.3.0 beta 2. - May 03 2005
Version 1.3.0 beta includes a check for invalid terminal window commands. Version 1.2.7 in KDE 3.4.1 also will include this. - Apr 15 2005
I'm starting to think about this one. There are a number of possibilities, and your views would help me design it.

There could be just a single named log file which KAlarm uses, or the user could choose a log file for each command alarm. Or alternatively, the log file could be automatically allocated by KAlarm, and accessible only through KAlarm.

If there is a separate log file for each alarm, how would you envisage accessing it? (Remember that the alarm might have expired after running.) Please give details of the user interface you'd like to see. - Apr 12 2005
Version 1.2.4 includes the improvements which you requested. Thanks - I'm sure other people will find them useful too. - Jan 09 2005
I have now implemented both of your suggestions in KDE CVS. The next version of KAlarm will include these facilities - hopefully it will be out within the next month. (Things are a bit slow just now because I have been setting up a new Debian system instead of my old SuSE 7.2.)

The Preferences dialogue allows you to choose which type of terminal window to use, or to enter command lines different from the preconfigured ones. I have done it so that the terminal window stays open after the command has run, so that the user can see the results (if any). (Although I haven't managed to discover any option for gnome-terminal to do that.) For xterm, that is done using 'xterm -hold -e'. Is that what you would expect? - Dec 23 2004
Run in terminal sounds like a sensible option to add. I'll consider providing the ability to edit a script. Thanks for the ideas. - Dec 10 2004
The current version can't do this, but version 1.2, which should be out fairly soon, will let you set up a repetition within a recurrence. - Aug 23 2004
Ah, of course, that must be the meaning! It sounds like a good idea as an option under 'command alarm', although I'm not sure how easy it would be to implement. I'll add it to the wish list. - May 25 2004
Version 1.1.0 Beta 3 which is now available, implements the 'stop sound' button in the alarm message window. - May 24 2004
Do you mean you want a DCOP browser to be displayed when the alarm triggers, instead of displaying a message, etc? I think that there is already a KDE DCOP display utility (called kdcop or something) - to do what you want, you could create a command alarm with a command line to activate it. Or have I misunderstood what you're wanting? - May 05 2004
This is a good idea, which I'm sure other people would like to see too. I'll implement it for the final 1.1.0 version. - Apr 26 2004
The new version 1.0.4 displays all types of sound file in the sound file selection dialogue (not just .wav files as before). - Feb 22 2004
You can select an mp3 file using the Sound file button, if you manually type in the file name. I will change the file selector options to show mp3 files as well as wav files. - Feb 15 2004