aboutsummaryrefslogtreecommitdiff
path: root/modules/devices.c
diff options
context:
space:
mode:
authorLeandro Pereira <leandro@hardinfo.org>2017-07-04 13:47:47 -0700
committerLeandro Pereira <leandro@hardinfo.org>2017-07-04 13:47:47 -0700
commit60131f4f0beb43ddb501a0ff114030c9c5f28b7d (patch)
tree21e3c1e83237c46b65f309c0265e9fb15ea80669 /modules/devices.c
parent9feaca9d2e36ef39fadad49a640a024b1adafe15 (diff)
Use load graph (used in memory view) to graph sensor data
Writing this I realized why I stopped working on HardInfo. While there are some good ideas in the architecture, it's API is beyond salvation. It's buggy, quirky, and not intuitive at all.
Diffstat (limited to 'modules/devices.c')
-rw-r--r--modules/devices.c20
1 files changed, 11 insertions, 9 deletions
diff --git a/modules/devices.c b/modules/devices.c
index 62fd790d..0cdb9a0d 100644
--- a/modules/devices.c
+++ b/modules/devices.c
@@ -489,16 +489,18 @@ gchar *callback_pci()
gchar *callback_sensors()
{
- return g_strdup_printf("[$ShellParam$]\n"
- "ColumnTitle$TextValue=Type\n"
- "ColumnTitle$Value=Driver\n"
- "ColumnTitle$Extra1=Sensor\n"
- "ColumnTitle$Extra2=Value\n"
+ return g_strdup_printf("[Sensors]\n"
+ "%s\n"
+ "[$ShellParam$]\n"
+ "ViewType=2\n"
+ "LoadGraphSuffix=\n"
+ "ColumnTitle$TextValue=Sensor\n"
+ "ColumnTitle$Value=Value\n"
+ "ColumnTitle$Extra1=Type\n"
"ShowColumnHeaders=true\n"
- "ReloadInterval=5000\n"
- "[Sensors]\n"
- "%s\n",
- sensors);
+ "RescanInterval=5000\n"
+ "%s",
+ sensors, lginterval);
}
gchar *callback_printers()