After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 690859 - Add sequences of tests
Add sequences of tests
Status: RESOLVED FIXED
Product: chronojump
Classification: Other
Component: chronojump
0.9.x
Other All
: Normal enhancement
: ---
Assigned To: Xavier de Blas
Xavier de Blas
Depends on:
Blocks:
 
 
Reported: 2012-12-29 17:01 UTC by Xavier de Blas
Modified: 2015-06-16 12:15 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Xavier de Blas 2012-12-29 17:01:27 UTC
a sequence means:

"some people ordered doing a test or some tests of same type"

Order is stored in PersonSession77 will be an "order" field. Then it can be used in the same session more times

src/sequence.cs will contain the order and the test or tests and the options

options:
-do n times
-repetitions consecutive or when all have done the test
-maybe more complexity if different tests have to be done, specially if user have to be inside or outside depending on the test

when a test has been done:
-show result: person, result
-have a list or persons and show who's next
-in respect to current test:
  -(1) every test can be cancelled or finished (if it's repetitive)
  -(2) allow to use it without pressing any "Start" button if user wants
  -(3) allow to discard that person or "do at the end"
-in respect to previous test: allow to delete it (as usual) and then same person will repeat or discard (3)
-allow to stop sequence
All this things can be shown under the "execute test" button or at the "test options" notebook

src/gui/sequence.cs will contain the gui that will be a partial of ChronoJumpWindow this will call the execution of tests, will have the control on cancelling... be a layer on the top of all the execute functionallity
There will be a "bool sequencyDoing" that will control the callbacks on ChronoJumpWindow

this sequencyDoing will also help in the sensitiveness of the buttons. Don't allow another test or sequency or user selection to be done while a sequencyDoing is true. Or deleting persons, loading them, creating tests, loading sessions, ...

maybe lot of sensitiveness have to be recorded to be restored after

on gui, (at jump, jumpRj, run, runInterval) "Select test" there will be at most right (bells if it's repetitive), and then at last position on right (sequence)