Rules script notification return, and notification center as implemented in Growl.framework 3.0

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Generate a notification using Growl.framework 3.0
2. Modify and return a notification using rules script
3. Return that notification center should be used
3. Note is displayed by Growl.framework in Notification Center

What is the expected output?
Node is displayed modified

What do you see instead?
Note is displayed unmodified

This 

Original issue reported on code.google.com by dan...@growl.info on 16 Aug 2013 at 3:33

[GoogleCodeExporter]

Sigh, hit enter in the wrong field before finished typing main message.  This 
is unrelated to the issue fixed in 2.1.1, in which the return wouldn't be used 
for NC messages generated within Growl (either bark or growl's own).  The cause 
of this is that when we detect Growl.framework 3.0 or newer, we send an NSDNC 
telling it to display that note UUID using NC.  We can't pass back a modified 
note since we are sandboxed, and the only real way to pass it back would be 
using the NSDNC payload at this time.  

Proposed solution next comment

Original comment by dan...@growl.info on 16 Aug 2013 at 3:36

[GoogleCodeExporter]

Proposed solution is that when the content of a notification has been modified 
to display using Growl's internal NC handler.  It's not perfect as it won't 
come from the sending app (without Bark), but it won't require a framework 
update to make work (it would be as if any other display style had been used).

I've set this on 2.1.2 for now, but the crashers already listed will take 
priority if we can make any headway on them.

Original comment by dan...@growl.info on 16 Aug 2013 at 3:42