Growl ticket shows temporarily in list

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start Growl.
2. Open the Growl preference pane.
3. Quit System Preferences.
4. Open the Growl preference pane again.

What is the expected output?
The Growl ticket appears either both times or never.

What do you see instead?
It appears the first time and is deleted by the second time.

Original issue reported on code.google.com by p...@growl.info on 14 May 2011 at 10:14

[GoogleCodeExporter]

The ticket is created when GHA registers with itself, and deleted when loading 
tickets (hence step 2 in the STR).

We should either make Growl's own notifications configurable, and delete the 
deletion on those grounds, or think of some way that Growl's notifications can 
be permanently enabled without creating a ticket, without opening a hole that 
applications could abuse.

Original comment by p...@growl.info on 14 May 2011 at 10:17

[GoogleCodeExporter]

Originally reported on discuss: 
http://groups.google.com/group/growldiscuss/t/28756538b191017e

Original comment by p...@growl.info on 14 May 2011 at 10:18

[GoogleCodeExporter]

I know we originally added the deleting of the Growl ticket because Chris 
thought that it would be confusing for Growl to have an entry for itself in 
itself.

I think the notifications we provided should be migrated out of the ticket and 
into the prefs window itself, that's not to say that we should get rid of the 
ticket, just not display it in that list. (settings amount to: growl 
notification on update available, user went idle, user returned).

-rudy

Original comment by rarich...@gmail.com on 15 May 2011 at 5:20

[GoogleCodeExporter]

the software update notification has already been pruned.

left behind: user went idle, user came back

we should push those settings into the prefs or remove them entirely, how 
useful are these notifications anyway?

Original comment by rarich...@gmail.com on 29 Jul 2011 at 3:53

[GoogleCodeExporter]

I think anything left in the growl ticket needs to be a preference as Rudy 
says. Not necessary for 1.3 though.

Original comment by chrisf.g...@gmail.com on 11 Aug 2011 at 6:19

• Added labels: Milestone-1.3

[GoogleCodeExporter]

user went idle and user came back have been pruned for 1.3, closing as fixed in 
source.

Original comment by rarich...@gmail.com on 22 Aug 2011 at 3:36

• Changed state: FixedInSource

[GoogleCodeExporter]

Original comment by ch...@growl.info on 4 Nov 2011 at 2:55

• Changed state: Fixed