Re: Re: GPE == *GNU* Palmtop Environment

Nils:

Can the rtcd first do an (single-instance) exec for the parent job of a
particular alarm and *then* send the PID (after it finds it, I guess) a
signal?

This would avoid the necessity of having to keep a job running while it
waits for an alarm, but shouldn't mess things up too much.

Also (or maybe instead?) can you break-out the acknowledge window from
gpe-alarm as something like gpe-announce so that others can use *this*
as the dialog window for alarms rather than having each program need to
write its own pop-up dialog for alarms?

Thanks.

Joe

PS. I have gpe-calendar now setting rtc alarms using rtcd rather than
relying on system calls to uschedule, but I don't actually have
gpe-calendar *do* anything with the signal(s) since I am not sure that
it wouldn't simply be better to have a central gpe-announce (or at least
an announcing widget in libgpewidget). (pb. I will commit these changes
to CVS soon :)

-- 
Joseph J. McCarthy, Assistant Professor
Department of Chemical and Petroleum Engineering
University of Pittsburgh
1249 Benedum Hall Pittsburgh, Pennsylvania 15261
Ph. 412-624-7362
Fax 412-624-9639
mccarthy@engrng.pitt.edu
http://granular.che.pitt.edu