xkmo / growl

Automatically exported from code.google.com/p/growl
0 stars 0 forks source link

Notifications get stuck on screen after attempting to close #414

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
(Not 100% sure)
1. Display a notification
2. Hover over the notification as it disappears or happen to click the location 
as the notification appears
3. Attempt to close the notification with the X button

What is the expected output?
Notification is closed/disappears

What do you see instead?
Notification is stuck on screen - no action removes the notification except for 
restarting Growl

What version of the product are you using? On what operating system?
Growl 1.3
Mac OSX 10.7.2

IMPORTANT NOTE: This is essentially a duplicate of a previous issue (located 
at: 
http://code.google.com/p/growl/issues/detail?id=348&can=1&q=stuck&colspec=ID%20T
ype%20Status%20Priority%20Milestone%20Owner%20BlockedOn%20Summary%20Product), 
but while the issue has been noted as being "FixedInSource", the last comment 
of the page states that reproducing the error as described has no current fix. 
Namely, "You can continue to quickly hover and over and it may go away, however 
if you clicked close, a flag is set that will get into a state you can't 
dismiss it no mater what steps you take."

Please provide any additional information below.

Original issue reported on code.google.com by bhsi...@gmail.com on 3 Jan 2012 at 3:06

GoogleCodeExporter commented 9 years ago
Update to 1.3.2.

Original comment by ch...@growl.info on 3 Jan 2012 at 3:12

GoogleCodeExporter commented 9 years ago
The version of Growl I'm running is one that I built myself from the source 
code. I don't see any changes made from the time I downloaded and compiled the 
application.

Original comment by bhsi...@gmail.com on 3 Jan 2012 at 3:15

GoogleCodeExporter commented 9 years ago
Which tag did you build? Which branch?

Original comment by ch...@growl.info on 3 Jan 2012 at 3:23

GoogleCodeExporter commented 9 years ago
I built the default branch/tag. I went ahead and updated to 1.3.2.

Originally, I didn't notice the presence of the different branches/tags. I was 
simply following the directions at 
http://growl.info/documentation/developer/growl-source-install.php and 
http://code.google.com/p/growl/source/checkout. Maybe the guide could go ahead 
and point out that users may want to check things out differently?

But all in all, thanks for the help! :)

Original comment by bhsi...@gmail.com on 3 Jan 2012 at 3:47

GoogleCodeExporter commented 9 years ago
Did that fix it for you?

Original comment by ch...@growl.info on 3 Jan 2012 at 3:50

GoogleCodeExporter commented 9 years ago
It should do the trick, yea.

Original comment by bhsi...@gmail.com on 3 Jan 2012 at 3:51

GoogleCodeExporter commented 9 years ago
Marking as Done

Original comment by dan...@growl.info on 1 Feb 2012 at 3:54