The GNTP path uses NSPropertyListSerialization on click contexts with NSPropertyListXMLFormat_v1_0 for its type for callbacks unless the object is a string, in which case its just sent as a String. This could potentially be handled better, and we would be willing to investigate that in the future.
The double feedback is a problem of the older frameworks needing NSDNC as its path for feedback, but GNTP also supporting it, however, we can't keep the connection alive forever (till the framework and Growl.app support the Keep-Alive socket system), much less support potential for double feedback should a user click a note in the rollup. The double feedback should only happen during the first 10 seconds or so. The different order of notifications is also potentially a side effect of the asynchronous, non keep-alive nature of the current framework. The current nature of our use of GCDAsyncSocket with a different socket for each note cycle (send, reply, feedback) results in a non fifo order. This will be improved with Keep-Alive, however, when exactly this will be implemented, is another matter. On Nov 20, 5:11 pm, Peter Hosey <[email protected]> wrote: > On Nov 20, 2011, at 15:05:06, Jakub Suder wrote: > > > I was passing the date inside the dictionary as NSDate, and I've noticed > > that the docs didn't list dates as allowed types for passing in the click > > context … > > An NSDate should work. I don't know why it was never listed on the docs, but > an NSDate is a valid property list object. > > > - the first time, the commit[date] field in the dictionary is passed > > as NSNumber, but on the second call (which shouldn't happen at all) > > that field is passed as NSString containing that number... > > My hunch is that this is a bug in how Growl deserializes plists from GNTP > communications, and/or how the framework serializes them to go over GNTP in > the first place. My other hunch is that the NSDate thing is as well. > > I suggest filing bugs on both of these: > > http://code.google.com/p/growl/issues/list -- 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.
