View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000528 | SpeedFan | Other | public | 2006-03-30 16:18 | 2006-06-02 11:10 |
| Reporter | walt | Assigned To | alfredo | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | acknowledged | Resolution | open | ||
| OS | Windows | OS Version | XP SP2 | ||
| Product Version | 4.28 | ||||
| Summary | 0000528: Testing Events and clarifying Article about Events | ||||
| Description | It would be a good enhancement to have a "TEST" button, or something similar, for testing events. While it would be best used to test an Execute, it might be also useful to see what a Pop Message will look like or what the Beep will sound like. Also, somewhat related, possibly you could enhance the online web Article about Events (http://www.almico.com/sfarticle.php?id=4) to talk about the need (or the lack of a need to) quote program names. In particular, and without a way to test, I am unsure if I need to quote a program name which contains a blank space (like if using a program from "c:\Program Files". Sometimes one needs to, and sometimes one doesn't. Also, does "Allow every ___ seconds" have a particular significance if set to "0". Does "0" zero mean continuously or just once? For a Beep, do you get just one beep, or a continuous beep? Thanks! | ||||
| Tags | No tags attached. | ||||
| Motherboard Model | |||||
| Video Card Model | |||||
|
|
Your suggestions are interesting and I'm actually working on some of them. About the "Allow every...", this is from that page: "This option causes the action not to be triggered if at least x seconds didn't pass since the last execution". If you set it to 0, it will be triggered whenever the condition is true. |
