I like your program, the whole idea is excellent, but I do have a few remarks.
1. Why only 1 global scan interval? Now my drives are doing a short read every 2 seconds, I can even hear one of it doing it outside my case. Unnecessary, it adds extra wear on the drive, hard drive streaming will be slightly interrupted every 2 sec and traditional hard drive temperatures never rise that fast. Many other tests will often not need that 2 sec interval either. Sure, I could raise the value, but that would also raise the value for the tests that do require a short interval.
2. Why can't I hide all non-monitored sensors with on click? It makes the sensor status screen easier to look at after all, how many people really want to see all the values presented and once a person takes the time to hide them manually, he risks to hit the Restore Original Order button by mistake one day, after which he has to go through the same tedious process again. There should at least be a confirmation window.
3. Why is data not saved when I make changes in the sensor status window? Do a test, change a value and leave the program by clicking the X in the top right corner: the data is not saved. It also happens in other areas. The only way for me to save it, is to press the large blue X in the bottom right corner, but that one closes the program.
4. This leads to the next question: why do you make it possible to close the program that easy? This is a monitoring program, some people will use it to protect their hardware. It's important that it ALWAYS runs, but in this case it's too easy to close it by mistake. A lot of monitor programs that I used, either turn the traditional Windows X into a "minimize to taskbar", ask for a confirmation or leave it up to the user how the X should function.
5. Why is there no documentation in the program? Here's an example, adding a value for alerting, in this case "Drive Warning", which can be either "yes" or "no", but the input field only expects a numeric value, since it pre-fills it with "0". I can enter yes or no, but the field is always 0 when I return.
Another example is the settings screen. TMP check, EC support, Evalute ACPI methods, Use HPET, SW SMI, etc....well you get the point, the majority will have no clue what you mean. Nobody expects a super detailed manual, but a least one sentence that describes in slightly more detail in a help file, so that we can do additional research ourselves if needed, would be very helpful.
1. Why only 1 global scan interval? Now my drives are doing a short read every 2 seconds, I can even hear one of it doing it outside my case. Unnecessary, it adds extra wear on the drive, hard drive streaming will be slightly interrupted every 2 sec and traditional hard drive temperatures never rise that fast. Many other tests will often not need that 2 sec interval either. Sure, I could raise the value, but that would also raise the value for the tests that do require a short interval.
2. Why can't I hide all non-monitored sensors with on click? It makes the sensor status screen easier to look at after all, how many people really want to see all the values presented and once a person takes the time to hide them manually, he risks to hit the Restore Original Order button by mistake one day, after which he has to go through the same tedious process again. There should at least be a confirmation window.
3. Why is data not saved when I make changes in the sensor status window? Do a test, change a value and leave the program by clicking the X in the top right corner: the data is not saved. It also happens in other areas. The only way for me to save it, is to press the large blue X in the bottom right corner, but that one closes the program.
4. This leads to the next question: why do you make it possible to close the program that easy? This is a monitoring program, some people will use it to protect their hardware. It's important that it ALWAYS runs, but in this case it's too easy to close it by mistake. A lot of monitor programs that I used, either turn the traditional Windows X into a "minimize to taskbar", ask for a confirmation or leave it up to the user how the X should function.
5. Why is there no documentation in the program? Here's an example, adding a value for alerting, in this case "Drive Warning", which can be either "yes" or "no", but the input field only expects a numeric value, since it pre-fills it with "0". I can enter yes or no, but the field is always 0 when I return.
Another example is the settings screen. TMP check, EC support, Evalute ACPI methods, Use HPET, SW SMI, etc....well you get the point, the majority will have no clue what you mean. Nobody expects a super detailed manual, but a least one sentence that describes in slightly more detail in a help file, so that we can do additional research ourselves if needed, would be very helpful.
