As of V 0.70.
Checkpoint warning can be set to any time / project / application, by adding <checkpoint> entries to the config.xml file.
<project> & <application> may be a partial name, or leave it blank for a general match.
<seconds> checkpoint time as displayed in seconds.
<red><green><blue> warning color in RGB.
This example always shows the checkpoint cells green. Red when the checkpoint time goes past 1 hour.
Disabling on a specific project.
The last project collatz conjecture always shows green, in effect disabling showing warnings on this project.
Make sure you place the projects you want to disable last.
Sequence:
The checkpoint colors are check in sequence, the last one in the list matching the project / application, is the one that's used.
<config>
<checkpoint>
<project>SETI</project>
<application>enhanced</application>
<seconds>0</seconds>
<red>0</red>
<green>255</green>
<blue>0</blue>
</checkpoint>
<checkpoint>
<project>SETI</project>
<application>enhanced</application>
<seconds>3600</seconds>
<red>255</red>
<green>0</green>
<blue>0</blue>
</checkpoint>
<checkpoint>
<project>collatz%20conjecture</project>
<application></application>
<seconds>0</seconds>
<red>0</red>
<green>255</green>
<blue>0</blue>
</checkpoint>
</config>
Warning:
Spaces are removed from the xml file.
Use %20 instead of a space.
So WORLD COMMUNITY GRID should be WORLD%20COMMUNITY%20GRID
The following characters are NOT allowed to be present in a text: < / >.
%3C = <
%2F = /
%3E = >
Upper and lower case are not used so: "WORLD" is exactly the same as "world".
The config.xml file should be located in the same folder and the exe.
Quote from: Pepo on August 25, 2010, 01:39:44 PM
<red>0</red>
Corrected, but will probably do the same thing. An invalid number = 0;
Quote from: fred on August 25, 2010, 01:54:39 PM
Quote from: Pepo on August 25, 2010, 01:39:44 PM
<red>0</red>
Corrected, but will probably do the same thing. An invalid number = 0;
Some code may go haywire or even the whole apps may crash upon swallowing
unexpected input ;D
(Hope it's not BT's case)
Quote from: Pepo on August 25, 2010, 02:25:55 PM
Some code may go haywire or even the whole apps may crash upon swallowing unexpected input ;D
(Hope it's not BT's case)
Always try to anticipate the unexpected ;D.