aboutsummaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorAdrian C. (anrxc) <anrxc@sysphere.org>2009-09-25 21:49:55 +0200
committerAdrian C. (anrxc) <anrxc@sysphere.org>2009-09-25 21:50:03 +0200
commitd2c60b35765a6261f6cc2a9f4586e8419a943870 (patch)
tree1ed0529e94dc82306b8ed34b3f29f95b1c275022 /README
parent56335fa86098d53e4d57ceb33d47ce1f8cd729d8 (diff)
downloadvicious-legacy-d2c60b35765a6261f6cc2a9f4586e8419a943870.tar.xz
README: clarified caching usage
Diffstat (limited to 'README')
-rw-r--r--README6
1 files changed, 4 insertions, 2 deletions
diff --git a/README b/README
index c70cf0a..a09155e 100644
--- a/README
+++ b/README
@@ -90,8 +90,10 @@ is one way to prevent widgets from draining your battery.
Vicious can also cache values returned by widget types. Caching
enables you to have multiple widgets using the same widget type and
-its worker function will be executed only once. It is useful mostly
-for widgets which do not require a special argument to be passed.
+its worker function will be executed only once. However be careful
+with those widgets that require a widget argument to be passed. If you
+are requesting information for different devices then caching is
+useless and can lead to confusion.
Update intervals also play a big role, and you can save a lot of power
with a smart approach to intervals. You should avoid intervals like: