Closed GoogleCodeExporter closed 8 years ago
Second that!
Original comment by and...@nodeone.se
on 21 Oct 2011 at 1:27
Absolutely, YES!
Original comment by bradvere...@gmail.com
on 8 Nov 2011 at 1:08
Guys and Gals, starring the issue is worth more than replying, since we can see
how many people starred the issue. :)
Original comment by ch...@growl.info
on 8 Nov 2011 at 2:52
Original comment by ch...@growl.info
on 8 Feb 2012 at 3:16
Starred and seconded. Thanks! :)
(Via
http://groups.google.com/group/growldiscuss/browse_thread/thread/4a06dc51e57964f
9?pli=1)
Original comment by lee...@gmail.com
on 18 Mar 2012 at 4:15
Should be merged with
http://code.google.com/p/growl/issues/detail?can=2&start=0&num=100&q=&colspec=ID
%20Type%20Status%20Priority%20Milestone%20Owner%20BlockedOn%20Summary%20Product&
groupby=&sort=&id=11 correct?
Original comment by lee...@gmail.com
on 18 Mar 2012 at 4:18
Fixed in 1.4.
Original comment by ch...@growl.info
on 18 Mar 2012 at 4:25
Should the Growl rollup not always get focus i.e. when you've been away and
return to unlock your screen? The Esc key does close the rollup for me, but I
hate that I have to focus the window even when it is the foremost application!
Original comment by niel.lam...@gmail.com
on 18 Mar 2012 at 4:28
Ah, yeah I see Escape works. But like Niel said, I want to be able to quickly
and reliably dismiss the rollup and get on with what I came back to my computer
for. Thanks for the attention!
Original comment by lee...@gmail.com
on 18 Mar 2012 at 4:31
There is no need for any further comment on this ticket. The ticket is closed
as fixedinsource for 1.4. Please look at the left side of this ticket.
Original comment by ch...@growl.info
on 18 Mar 2012 at 5:03
Fair enough. So I suppose there be a different ticket to force focus on the
rollup window. Here it is: http://code.google.com/p/growl/issues/detail?id=468
Original comment by lee...@gmail.com
on 19 Mar 2012 at 12:39
Issue 468 has been merged into this issue.
Original comment by ch...@growl.info
on 19 Mar 2012 at 7:51
Original comment by ch...@growl.info
on 11 Jan 2013 at 6:36
Original issue reported on code.google.com by
ch...@growl.info
on 14 Oct 2011 at 3:21