semi-infinite loop and the mess that is the notification dispatch controller

[GoogleCodeExporter]

screen space is reserved for plugins that care about such things via the 
GrowlPositioningController, when all available space has been reserved 
notifications are not queued up.  Thanks to a change Evan made to fix another 
bad behavior in the notification dispatch it will fire a timer every 5 seconds 
to check and see if space has become available.  It will do this for every 
single new notification that comes in.  So you will have x timers firing for x 
notifications, and if the screen remains full it will continue to get worse and 
worse.  between the timer firing and Growl logging "Could not display Growl 
notification; no screen space available." it eventually will get to the point 
where the process is using 80-90% CPU and doing nothing visible.

the GrowlPositionignController needs to be evaluated for correctness and 
recoded as necessary
the GrowlNotificationDisplayBridge and GrowlDisplayWindowController need to be 
evaluated and corrected so that a NSTimer is not required to "fix" out of space 
conditions.  

Original issue reported on code.google.com by rarich...@gmail.com on 20 Nov 2011 at 4:28

[GoogleCodeExporter]

Original comment by ch...@growl.info on 19 Jan 2012 at 10:44

• Changed state: Assigned

[GoogleCodeExporter]

Original comment by ch...@growl.info on 25 Jan 2012 at 10:42

[GoogleCodeExporter]

Original comment by ch...@growl.info on 30 Jan 2012 at 5:04

• Added labels: Milestone-2.0

[GoogleCodeExporter]

Growl 2.0 has a completely rewritten display system, and this is no longer an 
issue.  

Original comment by dan...@growl.info on 16 Jul 2012 at 8:26

• Changed state: FixedInSource

[GoogleCodeExporter]

Growl 2 is released, marking these as fixed.

Original comment by ch...@growl.info on 20 Sep 2012 at 3:16

[GoogleCodeExporter]

Original comment by ch...@growl.info on 11 Jan 2013 at 6:27

• Changed state: Fixed