Closed GoogleCodeExporter closed 9 years ago
Originally reported by Gerii4 on the discuss list, although I think somebody
else had filed it previously.
Original comment by prhgr...@gmail.com
on 29 Apr 2010 at 4:22
How long would it take to fix this? If it's more than 2 weeks, let's not hold
up 1.2.1
on this.
Original comment by chrisf.g...@gmail.com
on 30 Apr 2010 at 4:27
I don't think it will take two weeks. I have a fix half done—I thought it was
fully done, but it still doesn't work
yet, so I have more investigation to do.
Original comment by prhgr...@gmail.com
on 2 May 2010 at 7:25
Fine with me, let's make this the last fix for 1.2.1.
Original comment by chrisf.g...@gmail.com
on 2 May 2010 at 11:09
Two months later...
Original comment by alexchan...@gmail.com
on 20 Jun 2010 at 10:12
Fixed in http://growl.info/hg/growl-development/rev/f8b141f3deed .
Since the change had to go in GrowlApplicationBridge, and we have already
shipped Growl.framework 1.2.1, this change will not make it into G-WI.framework
1.2.1. It will appear in version 1.2.2 of both frameworks.
Original comment by prhgr...@gmail.com
on 20 Jun 2010 at 1:57
So without this, will there be a user version of Growl 1.2.1 anyway?
Original comment by alexchan...@gmail.com
on 21 Jun 2010 at 12:44
alexchandel: Huh?
Original comment by prhgr...@gmail.com
on 21 Jun 2010 at 6:05
oh oops, so will the Growl 1.2.1 framework be released with an installer (ie a
user package, rather than a framework for developers or source)? Btw, Growl's
domain has expired...
Original comment by alexchan...@gmail.com
on 27 Jun 2010 at 3:53
alexchandel: It's still not clear what you're asking. The
Growl-WithInstaller.framework version 1.2.1 will have the same design as
version 1.2.
Re the domain expiration: Thanks. We saw it and Chris fixed it today.
Original comment by prhgr...@gmail.com
on 27 Jun 2010 at 4:56
1.2.2 is released. Closing this issue.
Original comment by chrisf.g...@gmail.com
on 25 May 2011 at 2:21
Original comment by p...@growl.info
on 25 May 2011 at 10:21
Original issue reported on code.google.com by
prhgr...@gmail.com
on 29 Apr 2010 at 4:18