maemo.org Bugzilla – Bug 7743
libalarm API reference lacks details on time fields
Last modified: 2010-05-25 17:11:56 UTC
You need to
before you can comment on or make changes to this bug.
Copypaste from https://bugs.maemo.org/show_bug.cgi?id=6313:
Andre Klapper wrote:
> alarm_time = localtime(¤t_time);
> alarm_time->tm_sec += 2;
> event->alarm_tm = *alarm_time;
> The alarm is set 2 secs in to the future, however alarmd will
> round up the triggering time to the next full minute.
> If one really wants to specify triggering time with one second
> accuracy, then the event->alarm_time field can be used:
> event->alarm_time = time(0) + 2;
> Note: if alarm_time field is used, then the triggering time will
> not be adjusted when timezone changes.
> But if I'm not wrong these details are missing from the alarm api
Maemo SDK project manager is responsible of publishing Maemo API documents
because they are generated form Maemo SDK rootstrap sources. Reassigning this
to Soumya Bijjal.
I am no longer involved in Fremantle SDK. Moving to Marcell who is now the
Ok, so where should this triggering accuracy be documented? In the API
reference (generated from the code:
http://maemo.org/api_refs/5.0/5.0-final/libalarm/ ) or the Developer Guide
(In reply to comment #3)
> Ok, so where should this triggering accuracy be documented? In the API
> reference (generated from the code:
> http://maemo.org/api_refs/5.0/5.0-final/libalarm/ ) or the Developer Guide
> or both?
Both, but I already added a notebox to the Developer Guide (feel free to change
it), so only API reference is missing the info.
I have reported this internall to the team responsible for the alarmd
(In reply to comment #5)
> I have reported this internall to the team responsible for the alarmd
Fixed internally, will be released in PR1.2
Fixed internally. Fix will be included for the next public update.
[Rearrangement of Documentation bug reports.]
Mass-moving old closed Developer Platform > Documentation tickets.
You can filter bugmail by searching for this comment.