wshirey / growl

Automatically exported from code.google.com/p/growl
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Menu/Dock selection does not reflect current state at startup #594

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Per Yann:

I get two icons (Dock & Menu) whereas the General show only "Menu" as the 
current initial setting for icon position.

He can change the setting and then it works fine.

Original issue reported on code.google.com by ch...@growl.info on 20 Jun 2013 at 4:22

GoogleCodeExporter commented 8 years ago
I am confused by this, what startup does he mean? I have tried numerous forms 
of launching, fresh first launch, relaunch, logout/in with our start at login 
enabled, and cannot reproduce, when menu is set, all that shows up is menu in 
every case

Original comment by dan...@growl.info on 20 Jun 2013 at 4:43

GoogleCodeExporter commented 8 years ago
This one is not a very important feedback from me (if we can really reproduce 
it).
But the fact is that:

- the very first time I downloaded GrowlTunes2.2b5 on my 10.8.4 system
(where previous GrowlTunes had never been installed)
- when I manually launched GrowlTunes2.2b5 for the very first time
- I had not even played with any settings, only the default ones where present

=> and I could see:
1) Icon position set to "Menu" in settings (by default)
3) Nevertheless there where two icons visible, one in the menu and one in the 
Dock

Then, after changing myself the settings, everything is now OK, but the 
"default" settings seems to be not "normal".

Since this sandboxed app leaves settings in some files, I can't reproduce the 
totally fresh start from scratch and reproduce it to be sure.

Tell me where to clean up all the associated files for GrowlTunes and I'll 
experiment more precisely.

Original comment by yann.ric...@gmail.com on 20 Jun 2013 at 10:17

GoogleCodeExporter commented 8 years ago
Closing as Can't Reproduce.  I have tried on fresh users that are completely 
clean, and could not reproduce.  I have stepped through the all code related to 
this on launch under a variety of conditions and cannot reproduce.

For the record, under sandboxing, the only place we store anything is 
~/Library/Containers/<bundle identifier> (in this case com.growl.GrowlTunes), 
and deleting that removes all relevant state information.

Original comment by dan...@growl.info on 21 Jun 2013 at 10:15

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Thank you for the ~/Library/Containers/<bundle identifier> detail.

Then, like you, I tried to remove everything and restart from scratch to 
reproduce the strange behavior... But I can't.
So, you are right to close and forget it!

Original comment by yann.ric...@gmail.com on 22 Jun 2013 at 9:17