Hi,
I'm testing my app Gitifier (http://psionides.github.com/Gitifier)
with Growl 1.3.1 and SDK 1.3 on Lion. I've noticed two problems:
- if I send multiple notifications in a loop, they sometimes arrive in
a different order than they were sent in
- I'm getting such error in the console about 2 seconds after the
notifications appear:
Got disconnected: Error Domain=GCDAsyncSocketErrorDomain Code=4 "Read
operation timed out" UserInfo=0x400163920 {NSLocalizedDescription=Read
operation timed out}
This seems to have something to do with click contexts (even though I
don't actually click the notifications). I'm setting clickContext to a
dictionary that looks like this:
{
commit = {
authorEmail = "[email protected]";
authorName = "User 0";
date = "2011-11-20 18:07:57 +0000";
gitHash = ff7190da3d835a6d878f4f10fa558c50677db79f;
subject = commit2;
};
repository = "/Users/psionides/a";
}
If I set the clickContext to nil instead, the error in the console
doesn't appear, and the ordering problem doesn't seem to happen either
(although I can't be 100% sure because this doesn't happen every time
anyway, only one in a few times). If I set clickContext to something
simpler than a dictionary, e.g. a constant string, the problem
returns, so it's enough if it's different than nil.
Also, if I send one notification with clickContext=nil after a batch
with clickContext=dictionary, it almost always appears somewhere in
the middle of the batch or at the beginning. If it has a clickContext
like the rest then it usually appears properly at the end.
--
You received this message because you are subscribed to the Google Groups
"Growl Discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/growldiscuss?hl=en.
