View Single Post
Posts: 7 | Thanked: 1 time | Joined on Jul 2010
#272
Sorry for the double post...

I was having problems because I got the name of my script wrong. I did read over this thread earlier and I don't remember seeing any advice on how I could have detected this. I appreciate Alarmed is just modifying the configuration for Nokia's alarm software, but is there any way Alarmed could show e.g. a log of the output when (attempting to) run the command?

Although it wouldn't help if the command was more than a simple script invocation, it would help avoid this problem if the script to invoke could be chosen with the file browser.

Another small suggestion - I think it would be nicer to make the -C (CLI) switch the default, and have the .desktop file specify some other option (-D?) to tell the GUI to start. That way, command line users can just use it like a 'normal' CLI tool, and GUI users aren't any worse off.

I hope this isn't taken as whinging! Now I've cracked the incorrect name problem, this looks like exactly what I was looking for.

Cheers.