[Bug 417961] New: Temp table of repetitive events
- From: "chronojump (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>
- To: chronojump-devel-list gnome org
- Subject: [Bug 417961] New: Temp table of repetitive events
- Date: Tue, 13 Mar 2007 18:57:40 +0000 (UTC)
Do not reply to this via email (we are currently unable to handle email
responses and they get discarded). You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=417961
chronojump | chronojump | Ver: unspecified
Summary: Temp table of repetitive events
Product: chronojump
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: enhancement
Priority: Normal
Component: chronojump
AssignedTo: xaviblas cvs gnome org
ReportedBy: xaviblas cvs gnome org
QAContact: xaviblas cvs gnome org
GNOME version: Unspecified
GNOME milestone: Unspecified
IT will be nice to have a temp table for recording long events (long repetitive
jumps or intervallic runs). Then, if the software crashes or if there's any
other problem, chronojump should be able to recuperate that event until was
last recorded.
This events cannot be in normal jumpReactive or runInterval tables with a -1
id, because this can crash with other parts of the software. It will be easy to
create two special new tables for this:
-tempJumpReactive
-tempRunInterval
both with the same characteristics than jumpReactive and runInterval but they
will contain only 0 or 1 events. And every new event will have the value '1' as
uniqueID.
in jump, on the first 10 times it will be created the table, and then updated
every 10. In inteval run, it will be created at first subrun, and updated every
new subrun.
When event finish ok, the event on that row will be deleted.
On chronojump start (before loading any session), it will check if this event
exist, and if exists it will try to recover, and alert the user.
--
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]