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:49:55 +0200
commitb8f288b6e582b119bbbae25f89b152b131f2364a (patch)
treeb34fdbada1e84db6afcd173a102942ddd631b0f2 /README
parent46a7241015e33778f3174b65272ede2bb24c0252 (diff)
downloadvicious-legacy-b8f288b6e582b119bbbae25f89b152b131f2364a.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 d1b1458..7c3bc08 100644
--- a/README
+++ b/README
@@ -88,8 +88,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: