summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDave DeLong2010-03-19 14:31:40 -0600
committerDave DeLong2010-03-19 14:31:40 -0600
commit8f564da37891b67325f86b6b0ec80150056d3d52 (patch)
tree11cfbff17ee7fc3ff25e7c8b3d5edb03af43b04f
parentd73fb995487574ddeabd5d0799895b71c40cacf3 (diff)
downloadDDHotKey-8f564da37891b67325f86b6b0ec80150056d3d52.tar.bz2
Minor API clarification (target and object memory management)
-rw-r--r--README.markdown5
1 files changed, 3 insertions, 2 deletions
diff --git a/README.markdown b/README.markdown
index ab3543a..c0c90eb 100644
--- a/README.markdown
+++ b/README.markdown
@@ -30,8 +30,9 @@ alloc/init and release a `DDHotKeyCenter` object at anytime; it is merely an acc
You can register a hotkey in one of two ways: via a target/action mechanism, or with a block. The
target/action mechanism can take a single extra "object" parameter, which it will pass into the
-action when the hotkey is fired. In addition, an `NSEvent` object is passed, which contains
-information regarding the hotkey event (such as the location, the keyCode, the modifierFlags, etc).
+action when the hotkey is fired. Both the `target` and the `object` parameters are retained by the
+`DDHotKeyCenter`. In addition, an `NSEvent` object is passed, which contains information regarding
+the hotkey event (such as the location, the keyCode, the modifierFlags, etc).
Hotkey actions must have one of two method signatures (the actual selector is irrelevant):