http://www.handhelds.org/~bugzilla/show_bug.cgi?id=1552
[email protected] changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|[email protected] |[email protected]
Status|ASSIGNED |NEW
------- Additional Comments From [email protected] 2006-05-01 09:40 -------
I am 99.9% sure this is a gpe-calendar bug. In the alarm code, I try to keep
track of which alarm is going off so that it no longer can go off, but
apparently it doesn't work. Another viable option is to use the "next_alarm_id"
table in some way (this is a table currently used only for x86 operation of
gpe-calendar/libschedule, so it should be easy to add something without
dramatically changing the overall behavior of the suite). This would also make
it machine dependent (since I do not want anyone to ever sync the next_alarm_id
table) so that you don't get weird behavior when syncing.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.