I would like to prevent my Growl For Windows installation from
automatically checking for updates. Unlike the original Mac version,
I cannot see a UI option for this, but the config file does have
"AutomaticallyCheckForUpdates". I manually set this to False, but I
still get the prompt after restarting everything.
Am I doing something really stupid, or does Growl For Windows not
respect this setting?
Growl for Windows does use and respect the AutomaticallyCheckForUpdates setting. To manually modify it, you have to make sure Growl is not running at all, then modify the file and save it, then re-launch Growl.
On Mon, Jan 16, 2012 at 7:55 AM, Ned Lowe <ned.l...@gmail.com> wrote: > Hi,
> I would like to prevent my Growl For Windows installation from > automatically checking for updates. Unlike the original Mac version, > I cannot see a UI option for this, but the config file does have > "AutomaticallyCheckForUpdates". I manually set this to False, but I > still get the prompt after restarting everything.
> Am I doing something really stupid, or does Growl For Windows not > respect this setting?
> Thanks, > Ned
> -- > You received this message because you are subscribed to the Google Groups "growl for windows" group. > To post to this group, send email to growl-for-windows@googlegroups.com. > To unsubscribe from this group, send email to growl-for-windows+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/growl-for-windows?hl=en.
> Growl for Windows does use and respect the
> AutomaticallyCheckForUpdates setting. To manually modify it, you have
> to make sure Growl is not running at all, then modify the file and
> save it, then re-launch Growl.
> On Mon, Jan 16, 2012 at 7:55 AM, Ned Lowe <ned.l...@gmail.com> wrote:
> > Hi,
> > I would like to prevent my Growl For Windows installation from
> > automatically checking for updates. Unlike the original Mac version,
> > I cannot see a UI option for this, but the config file does have
> > "AutomaticallyCheckForUpdates". I manually set this to False, but I
> > still get the prompt after restarting everything.
> > Am I doing something really stupid, or does Growl For Windows not
> > respect this setting?
> > Thanks,
> > Ned
> > --
> > You received this message because you are subscribed to the Google Groups "growl for windows" group.
> > To post to this group, send email to growl-for-windows@googlegroups.com.
> > To unsubscribe from this group, send email to growl-for-windows+unsubscribe@googlegroups.com.
> > For more options, visit this group athttp://groups.google.com/group/growl-for-windows?hl=en.
You are not crazy - I just checked everything again and found the source of the trouble. Growl does use and honor the AutomaticallyCheckForUpdates setting, but only *after* the initial check at startup. So right now, it always checks when you first launch the app, and normally, would then check every 24 hours thereafter. If you set AutomaticallyCheckForUpdates to false, it wont keep checking every 24 hours, but it still does the initial check.
I dont remember exactly why I set it up that way, but at least it all makes sense now as to why it was still checking. I will take a look back through my release notes and see if there is any reason why I left it working that way or not.
Thanks for sticking with this and helping me find the root cause.
> But when Growl loads, it asks me to update (after about 10 seconds).
> I'm running Growl 2.0.6.1 (I haven't updated deliberately so I can > check the behaviour).
> Thanks, > Ned
> (sorry for the cutoff message before)
> On Jan 26, 1:22 am, Brian Dunnington <briandunning...@gmail.com> > wrote: >> Growl for Windows does use and respect the >> AutomaticallyCheckForUpdates setting. To manually modify it, you have >> to make sure Growl is not running at all, then modify the file and >> save it, then re-launch Growl.
>> On Mon, Jan 16, 2012 at 7:55 AM, Ned Lowe <ned.l...@gmail.com> wrote: >> > Hi,
>> > I would like to prevent my Growl For Windows installation from >> > automatically checking for updates. Unlike the original Mac version, >> > I cannot see a UI option for this, but the config file does have >> > "AutomaticallyCheckForUpdates". I manually set this to False, but I >> > still get the prompt after restarting everything.
>> > Am I doing something really stupid, or does Growl For Windows not >> > respect this setting?
>> > Thanks, >> > Ned
>> > -- >> > You received this message because you are subscribed to the Google Groups "growl for windows" group. >> > To post to this group, send email to growl-for-windows@googlegroups.com. >> > To unsubscribe from this group, send email to growl-for-windows+unsubscribe@googlegroups.com. >> > For more options, visit this group athttp://groups.google.com/group/growl-for-windows?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "growl for windows" group. > To post to this group, send email to growl-for-windows@googlegroups.com. > To unsubscribe from this group, send email to growl-for-windows+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/growl-for-windows?hl=en.
> wrote: > You are not crazy - I just checked everything again and found the > source of the trouble. Growl does use and honor the > AutomaticallyCheckForUpdates setting, but only *after* the initial > check at startup. So right now, it always checks when you first launch > the app, and normally, would then check every 24 hours thereafter. If > you set AutomaticallyCheckForUpdates to false, it wont keep checking > every 24 hours, but it still does the initial check.
> I dont remember exactly why I set it up that way, but at least it all > makes sense now as to why it was still checking. I will take a look > back through my release notes and see if there is any reason why I > left it working that way or not.
> Thanks for sticking with this and helping me find the root cause.
> On Sun, Feb 12, 2012 at 11:10 PM, Ned Lowe <ned.l...@gmail.com> wrote: > > Hi,
> > I've checked and double-checked, I definitely have the following in my > > config file:
> > But when Growl loads, it asks me to update (after about 10 seconds).
> > I'm running Growl 2.0.6.1 (I haven't updated deliberately so I can > > check the behaviour).
> > Thanks, > > Ned
> > (sorry for the cutoff message before)
> > On Jan 26, 1:22 am, Brian Dunnington <briandunning...@gmail.com> > > wrote: > >> Growl for Windows does use and respect the > >> AutomaticallyCheckForUpdates setting. To manually modify it, you have > >> to make sure Growl is not running at all, then modify the file and > >> save it, then re-launch Growl.
> >> On Mon, Jan 16, 2012 at 7:55 AM, Ned Lowe <ned.l...@gmail.com> wrote: > >> > Hi,
> >> > I would like to prevent my Growl For Windows installation from > >> > automatically checking for updates. Unlike the original Mac version, > >> > I cannot see a UI option for this, but the config file does have > >> > "AutomaticallyCheckForUpdates". I manually set this to False, but I > >> > still get the prompt after restarting everything.
> >> > Am I doing something really stupid, or does Growl For Windows not > >> > respect this setting?
> >> > Thanks, > >> > Ned
> >> > -- > >> > You received this message because you are subscribed to the Google > Groups "growl for windows" group. > >> > To post to this group, send email to > growl-for-windows@googlegroups.com. > >> > To unsubscribe from this group, send email to > growl-for-windows+unsubscribe@googlegroups.com. > >> > For more options, visit this group athttp:// > groups.google.com/group/growl-for-windows?hl=en.
> > -- > > You received this message because you are subscribed to the Google > Groups "growl for windows" group. > > To post to this group, send email to growl-for-windows@googlegroups.com. > > To unsubscribe from this group, send email to > growl-for-windows+unsubscribe@googlegroups.com. > > For more options, visit this group at > http://groups.google.com/group/growl-for-windows?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "growl for windows" group. > To post to this group, send email to growl-for-windows@googlegroups.com. > To unsubscribe from this group, send email to > growl-for-windows+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/growl-for-windows?hl=en.
Any update on this? The use case is that in the place where I deploy
Growl For Windows, the users are pretty locked down - and so can't
install anything. This means the popup they get when new versions are
released is pretty annoying to them.
Many thanks,
Ned
On Feb 17, 10:46 am, Ned Lowe <ned.l...@gmail.com> wrote:
> Thanks Brian - that's much appreciated. Please let me know if/when this can
> be changed.
> On Tue, Feb 14, 2012 at 1:47 AM, Brian Dunnington <briandunning...@gmail.com
> > wrote:
> > You are not crazy - I just checked everything again and found the
> > source of the trouble. Growl does use and honor the
> > AutomaticallyCheckForUpdates setting, but only *after* the initial
> > check at startup. So right now, it always checks when you first launch
> > the app, and normally, would then check every 24 hours thereafter. If
> > you set AutomaticallyCheckForUpdates to false, it wont keep checking
> > every 24 hours, but it still does the initial check.
> > I dont remember exactly why I set it up that way, but at least it all
> > makes sense now as to why it was still checking. I will take a look
> > back through my release notes and see if there is any reason why I
> > left it working that way or not.
> > Thanks for sticking with this and helping me find the root cause.
> > On Sun, Feb 12, 2012 at 11:10 PM, Ned Lowe <ned.l...@gmail.com> wrote:
> > > Hi,
> > > I've checked and double-checked, I definitely have the following in my
> > > config file:
> > > But when Growl loads, it asks me to update (after about 10 seconds).
> > > I'm running Growl 2.0.6.1 (I haven't updated deliberately so I can
> > > check the behaviour).
> > > Thanks,
> > > Ned
> > > (sorry for the cutoff message before)
> > > On Jan 26, 1:22 am, Brian Dunnington <briandunning...@gmail.com>
> > > wrote:
> > >> Growl for Windows does use and respect the
> > >> AutomaticallyCheckForUpdates setting. To manually modify it, you have
> > >> to make sure Growl is not running at all, then modify the file and
> > >> save it, then re-launch Growl.
> > >> On Mon, Jan 16, 2012 at 7:55 AM, Ned Lowe <ned.l...@gmail.com> wrote:
> > >> > Hi,
> > >> > I would like to prevent my Growl For Windows installation from
> > >> > automatically checking for updates. Unlike the original Mac version,
> > >> > I cannot see a UI option for this, but the config file does have
> > >> > "AutomaticallyCheckForUpdates". I manually set this to False, but I
> > >> > still get the prompt after restarting everything.
> > >> > Am I doing something really stupid, or does Growl For Windows not
> > >> > respect this setting?
> > >> > Thanks,
> > >> > Ned
> > >> > --
> > >> > You received this message because you are subscribed to the Google
> > Groups "growl for windows" group.
> > >> > To post to this group, send email to
> > growl-for-windows@googlegroups.com.
> > >> > To unsubscribe from this group, send email to
> > growl-for-windows+unsubscribe@googlegroups.com.
> > >> > For more options, visit this group athttp://
> > groups.google.com/group/growl-for-windows?hl=en.
> > > --
> > > You received this message because you are subscribed to the Google
> > Groups "growl for windows" group.
> > > To post to this group, send email to growl-for-windows@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > growl-for-windows+unsubscribe@googlegroups.com.
> > > For more options, visit this group at
> >http://groups.google.com/group/growl-for-windows?hl=en.
> > --
> > You received this message because you are subscribed to the Google Groups
> > "growl for windows" group.
> > To post to this group, send email to growl-for-windows@googlegroups.com.
> > To unsubscribe from this group, send email to
> > growl-for-windows+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/growl-for-windows?hl=en.
Just out of curiosity, when you say you modified your config file, what is the file location and name of the file you are editing?
I did some more testing this morning to make sure I had found the root cause, but I think I misspoke earlier when I said that Growl still does one check upon launch even if AutomaticallyCheckForUpdates is set to false. It does *not* seem to do that when I debug it and step through the code, so I want to be sure that I understand how you are approaching it so I can duplicate your behavior before I change anything.
On Wed, Mar 7, 2012 at 4:51 PM, Ned Lowe <ned.l...@gmail.com> wrote: > Hi Brian,
> Any update on this? The use case is that in the place where I deploy > Growl For Windows, the users are pretty locked down - and so can't > install anything. This means the popup they get when new versions are > released is pretty annoying to them.
> Many thanks, > Ned
> On Feb 17, 10:46 am, Ned Lowe <ned.l...@gmail.com> wrote: >> Thanks Brian - that's much appreciated. Please let me know if/when this can >> be changed.
>> On Tue, Feb 14, 2012 at 1:47 AM, Brian Dunnington <briandunning...@gmail.com
>> > wrote: >> > You are not crazy - I just checked everything again and found the >> > source of the trouble. Growl does use and honor the >> > AutomaticallyCheckForUpdates setting, but only *after* the initial >> > check at startup. So right now, it always checks when you first launch >> > the app, and normally, would then check every 24 hours thereafter. If >> > you set AutomaticallyCheckForUpdates to false, it wont keep checking >> > every 24 hours, but it still does the initial check.
>> > I dont remember exactly why I set it up that way, but at least it all >> > makes sense now as to why it was still checking. I will take a look >> > back through my release notes and see if there is any reason why I >> > left it working that way or not.
>> > Thanks for sticking with this and helping me find the root cause.
>> > On Sun, Feb 12, 2012 at 11:10 PM, Ned Lowe <ned.l...@gmail.com> wrote: >> > > Hi,
>> > > I've checked and double-checked, I definitely have the following in my >> > > config file:
>> > > But when Growl loads, it asks me to update (after about 10 seconds).
>> > > I'm running Growl 2.0.6.1 (I haven't updated deliberately so I can >> > > check the behaviour).
>> > > Thanks, >> > > Ned
>> > > (sorry for the cutoff message before)
>> > > On Jan 26, 1:22 am, Brian Dunnington <briandunning...@gmail.com> >> > > wrote: >> > >> Growl for Windows does use and respect the >> > >> AutomaticallyCheckForUpdates setting. To manually modify it, you have >> > >> to make sure Growl is not running at all, then modify the file and >> > >> save it, then re-launch Growl.
>> > >> On Mon, Jan 16, 2012 at 7:55 AM, Ned Lowe <ned.l...@gmail.com> wrote: >> > >> > Hi,
>> > >> > I would like to prevent my Growl For Windows installation from >> > >> > automatically checking for updates. Unlike the original Mac version, >> > >> > I cannot see a UI option for this, but the config file does have >> > >> > "AutomaticallyCheckForUpdates". I manually set this to False, but I >> > >> > still get the prompt after restarting everything.
>> > >> > Am I doing something really stupid, or does Growl For Windows not >> > >> > respect this setting?
>> > >> > Thanks, >> > >> > Ned
>> > >> > -- >> > >> > You received this message because you are subscribed to the Google >> > Groups "growl for windows" group. >> > >> > To post to this group, send email to >> > growl-for-windows@googlegroups.com. >> > >> > To unsubscribe from this group, send email to >> > growl-for-windows+unsubscribe@googlegroups.com. >> > >> > For more options, visit this group athttp:// >> > groups.google.com/group/growl-for-windows?hl=en.
>> > > -- >> > > You received this message because you are subscribed to the Google >> > Groups "growl for windows" group. >> > > To post to this group, send email to growl-for-windows@googlegroups.com. >> > > To unsubscribe from this group, send email to >> > growl-for-windows+unsubscribe@googlegroups.com. >> > > For more options, visit this group at >> >http://groups.google.com/group/growl-for-windows?hl=en.
>> > -- >> > You received this message because you are subscribed to the Google Groups >> > "growl for windows" group. >> > To post to this group, send email to growl-for-windows@googlegroups.com. >> > To unsubscribe from this group, send email to >> > growl-for-windows+unsubscribe@googlegroups.com. >> > For more options, visit this group at >> >http://groups.google.com/group/growl-for-windows?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "growl for windows" group. > To post to this group, send email to growl-for-windows@googlegroups.com. > To unsubscribe from this group, send email to growl-for-windows+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/growl-for-windows?hl=en.
Last call for more info on this. I am planning to put out a new build very soon and would like to include the fix for this if it is still an issue for you, but I was unable to reproduce it when I actually tried to debug it. If you are editing the growl.exe.config file, that is the cause of the issue (the settings are read from each individual user's user.config file in their %LOCALAPPDATA% location instead).
<briandunning...@gmail.com> wrote: > Just out of curiosity, when you say you modified your config file, > what is the file location and name of the file you are editing?
> I did some more testing this morning to make sure I had found the root > cause, but I think I misspoke earlier when I said that Growl still > does one check upon launch even if AutomaticallyCheckForUpdates is set > to false. It does *not* seem to do that when I debug it and step > through the code, so I want to be sure that I understand how you are > approaching it so I can duplicate your behavior before I change > anything.
> On Wed, Mar 7, 2012 at 4:51 PM, Ned Lowe <ned.l...@gmail.com> wrote: >> Hi Brian,
>> Any update on this? The use case is that in the place where I deploy >> Growl For Windows, the users are pretty locked down - and so can't >> install anything. This means the popup they get when new versions are >> released is pretty annoying to them.
>> Many thanks, >> Ned
>> On Feb 17, 10:46 am, Ned Lowe <ned.l...@gmail.com> wrote: >>> Thanks Brian - that's much appreciated. Please let me know if/when this can >>> be changed.
>>> On Tue, Feb 14, 2012 at 1:47 AM, Brian Dunnington <briandunning...@gmail.com
>>> > wrote: >>> > You are not crazy - I just checked everything again and found the >>> > source of the trouble. Growl does use and honor the >>> > AutomaticallyCheckForUpdates setting, but only *after* the initial >>> > check at startup. So right now, it always checks when you first launch >>> > the app, and normally, would then check every 24 hours thereafter. If >>> > you set AutomaticallyCheckForUpdates to false, it wont keep checking >>> > every 24 hours, but it still does the initial check.
>>> > I dont remember exactly why I set it up that way, but at least it all >>> > makes sense now as to why it was still checking. I will take a look >>> > back through my release notes and see if there is any reason why I >>> > left it working that way or not.
>>> > Thanks for sticking with this and helping me find the root cause.
>>> > On Sun, Feb 12, 2012 at 11:10 PM, Ned Lowe <ned.l...@gmail.com> wrote: >>> > > Hi,
>>> > > I've checked and double-checked, I definitely have the following in my >>> > > config file:
>>> > > But when Growl loads, it asks me to update (after about 10 seconds).
>>> > > I'm running Growl 2.0.6.1 (I haven't updated deliberately so I can >>> > > check the behaviour).
>>> > > Thanks, >>> > > Ned
>>> > > (sorry for the cutoff message before)
>>> > > On Jan 26, 1:22 am, Brian Dunnington <briandunning...@gmail.com> >>> > > wrote: >>> > >> Growl for Windows does use and respect the >>> > >> AutomaticallyCheckForUpdates setting. To manually modify it, you have >>> > >> to make sure Growl is not running at all, then modify the file and >>> > >> save it, then re-launch Growl.
>>> > >> On Mon, Jan 16, 2012 at 7:55 AM, Ned Lowe <ned.l...@gmail.com> wrote: >>> > >> > Hi,
>>> > >> > I would like to prevent my Growl For Windows installation from >>> > >> > automatically checking for updates. Unlike the original Mac version, >>> > >> > I cannot see a UI option for this, but the config file does have >>> > >> > "AutomaticallyCheckForUpdates". I manually set this to False, but I >>> > >> > still get the prompt after restarting everything.
>>> > >> > Am I doing something really stupid, or does Growl For Windows not >>> > >> > respect this setting?
>>> > >> > Thanks, >>> > >> > Ned
>>> > >> > -- >>> > >> > You received this message because you are subscribed to the Google >>> > Groups "growl for windows" group. >>> > >> > To post to this group, send email to >>> > growl-for-windows@googlegroups.com. >>> > >> > To unsubscribe from this group, send email to >>> > growl-for-windows+unsubscribe@googlegroups.com. >>> > >> > For more options, visit this group athttp:// >>> > groups.google.com/group/growl-for-windows?hl=en.
>>> > > -- >>> > > You received this message because you are subscribed to the Google >>> > Groups "growl for windows" group. >>> > > To post to this group, send email to growl-for-windows@googlegroups.com. >>> > > To unsubscribe from this group, send email to >>> > growl-for-windows+unsubscribe@googlegroups.com. >>> > > For more options, visit this group at >>> >http://groups.google.com/group/growl-for-windows?hl=en.
>>> > -- >>> > You received this message because you are subscribed to the Google Groups >>> > "growl for windows" group. >>> > To post to this group, send email to growl-for-windows@googlegroups.com. >>> > To unsubscribe from this group, send email to >>> > growl-for-windows+unsubscribe@googlegroups.com. >>> > For more options, visit this group at >>> >http://groups.google.com/group/growl-for-windows?hl=en.
>> -- >> You received this message because you are subscribed to the Google Groups "growl for windows" group. >> To post to this group, send email to growl-for-windows@googlegroups.com. >> To unsubscribe from this group, send email to growl-for-windows+unsubscribe@googlegroups.com. >> For more options, visit this group at http://groups.google.com/group/growl-for-windows?hl=en.
Very sorry Brian - no idea how I managed to miss TWO mails from you. My sincere apologies - I don't use gmail for anything except this group.
OK - yes I was editing the growl.exe.config file bundled with the main exe.
We don't have %LOCALAPPDATA% (just %APPDATA%), but we do have the Local AppData registry key. I checked the folder specified by that key - and sure enough, there is a Growl folder, including a config file with CheckForUpdates set to True. Apologies, I didn't realise there were two.
What would be your recommendation for getting that file deployed with 'False' set. I can't get users to change it themselves, but arguably I could write a script that changed it.
My ideal scenario would be when that file gets created it takes the 'parent' value from the growl.exe.config. Is that possible at all?
Many thanks - and sorry again, Ned
On Tue, Mar 20, 2012 at 2:16 AM, Brian Dunnington <briandunning...@gmail.com
> wrote: > Last call for more info on this. I am planning to put out a new build > very soon and would like to include the fix for this if it is still an > issue for you, but I was unable to reproduce it when I actually tried > to debug it. If you are editing the growl.exe.config file, that is the > cause of the issue (the settings are read from each individual user's > user.config file in their %LOCALAPPDATA% location instead).
> On Fri, Mar 9, 2012 at 8:54 AM, Brian Dunnington > <briandunning...@gmail.com> wrote: > > Just out of curiosity, when you say you modified your config file, > > what is the file location and name of the file you are editing?
> > I did some more testing this morning to make sure I had found the root > > cause, but I think I misspoke earlier when I said that Growl still > > does one check upon launch even if AutomaticallyCheckForUpdates is set > > to false. It does *not* seem to do that when I debug it and step > > through the code, so I want to be sure that I understand how you are > > approaching it so I can duplicate your behavior before I change > > anything.
> > On Wed, Mar 7, 2012 at 4:51 PM, Ned Lowe <ned.l...@gmail.com> wrote: > >> Hi Brian,
> >> Any update on this? The use case is that in the place where I deploy > >> Growl For Windows, the users are pretty locked down - and so can't > >> install anything. This means the popup they get when new versions are > >> released is pretty annoying to them.
> >> Many thanks, > >> Ned
> >> On Feb 17, 10:46 am, Ned Lowe <ned.l...@gmail.com> wrote: > >>> Thanks Brian - that's much appreciated. Please let me know if/when > this can > >>> be changed.
> >>> On Tue, Feb 14, 2012 at 1:47 AM, Brian Dunnington < > briandunning...@gmail.com
> >>> > wrote: > >>> > You are not crazy - I just checked everything again and found the > >>> > source of the trouble. Growl does use and honor the > >>> > AutomaticallyCheckForUpdates setting, but only *after* the initial > >>> > check at startup. So right now, it always checks when you first > launch > >>> > the app, and normally, would then check every 24 hours thereafter. If > >>> > you set AutomaticallyCheckForUpdates to false, it wont keep checking > >>> > every 24 hours, but it still does the initial check.
> >>> > I dont remember exactly why I set it up that way, but at least it all > >>> > makes sense now as to why it was still checking. I will take a look > >>> > back through my release notes and see if there is any reason why I > >>> > left it working that way or not.
> >>> > Thanks for sticking with this and helping me find the root cause.
> >>> > On Sun, Feb 12, 2012 at 11:10 PM, Ned Lowe <ned.l...@gmail.com> > wrote: > >>> > > Hi,
> >>> > > I've checked and double-checked, I definitely have the following > in my > >>> > > config file:
> >>> > > But when Growl loads, it asks me to update (after about 10 > seconds).
> >>> > > I'm running Growl 2.0.6.1 (I haven't updated deliberately so I can > >>> > > check the behaviour).
> >>> > > Thanks, > >>> > > Ned
> >>> > > (sorry for the cutoff message before)
> >>> > > On Jan 26, 1:22 am, Brian Dunnington <briandunning...@gmail.com> > >>> > > wrote: > >>> > >> Growl for Windows does use and respect the > >>> > >> AutomaticallyCheckForUpdates setting. To manually modify it, you > have > >>> > >> to make sure Growl is not running at all, then modify the file and > >>> > >> save it, then re-launch Growl.
> >>> > >> On Mon, Jan 16, 2012 at 7:55 AM, Ned Lowe <ned.l...@gmail.com> > wrote: > >>> > >> > Hi,
> >>> > >> > I would like to prevent my Growl For Windows installation from > >>> > >> > automatically checking for updates. Unlike the original Mac > version, > >>> > >> > I cannot see a UI option for this, but the config file does have > >>> > >> > "AutomaticallyCheckForUpdates". I manually set this to False, > but I > >>> > >> > still get the prompt after restarting everything.
> >>> > >> > Am I doing something really stupid, or does Growl For Windows > not > >>> > >> > respect this setting?
> >>> > >> > Thanks, > >>> > >> > Ned
> >>> > >> > -- > >>> > >> > You received this message because you are subscribed to the > Google > >>> > Groups "growl for windows" group. > >>> > >> > To post to this group, send email to > >>> > growl-for-windows@googlegroups.com. > >>> > >> > To unsubscribe from this group, send email to > >>> > growl-for-windows+unsubscribe@googlegroups.com. > >>> > >> > For more options, visit this group athttp:// > >>> > groups.google.com/group/growl-for-windows?hl=en.
> >>> > > -- > >>> > > You received this message because you are subscribed to the Google > >>> > Groups "growl for windows" group. > >>> > > To post to this group, send email to > growl-for-windows@googlegroups.com. > >>> > > To unsubscribe from this group, send email to > >>> > growl-for-windows+unsubscribe@googlegroups.com. > >>> > > For more options, visit this group at > >>> >http://groups.google.com/group/growl-for-windows?hl=en.
> >>> > -- > >>> > You received this message because you are subscribed to the Google > Groups > >>> > "growl for windows" group. > >>> > To post to this group, send email to > growl-for-windows@googlegroups.com. > >>> > To unsubscribe from this group, send email to > >>> > growl-for-windows+unsubscribe@googlegroups.com. > >>> > For more options, visit this group at > >>> >http://groups.google.com/group/growl-for-windows?hl=en.
> >> -- > >> You received this message because you are subscribed to the Google > Groups "growl for windows" group. > >> To post to this group, send email to growl-for-windows@googlegroups.com > . > >> To unsubscribe from this group, send email to > growl-for-windows+unsubscribe@googlegroups.com. > >> For more options, visit this group at > http://groups.google.com/group/growl-for-windows?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "growl for windows" group. > To post to this group, send email to growl-for-windows@googlegroups.com. > To unsubscribe from this group, send email to > growl-for-windows+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/growl-for-windows?hl=en.
No worries - glad we got to the root of the problem.
Up until v2.0.9 (just released yesterday), there was a bug that prevented the default values in growl.exe.config from being used. That bug has been fixed though, so you should be able to achieve your scenario now. If you edit the growl.exe.config file, those values will be used for each *new* user on the machine. So if a user has not run Growl before (which, if you just installed it, should be the case), then when they first run it, Growl will create the user.config file, copying the growl.exe.config values. Note that if a user has already ran Growl and their user.config already exists, then editing the growl.exe.config will have no effect for that user.
Try that out and let me know if that works for what you are doing.
On Wed, Mar 21, 2012 at 10:54 PM, Ned Lowe <ned.l...@gmail.com> wrote: > Very sorry Brian - no idea how I managed to miss TWO mails from you. My > sincere apologies - I don't use gmail for anything except this group.
> OK - yes I was editing the growl.exe.config file bundled with the main exe.
> We don't have %LOCALAPPDATA% (just %APPDATA%), but we do have the Local > AppData registry key. I checked the folder specified by that key - and sure > enough, there is a Growl folder, including a config file with > CheckForUpdates set to True. Apologies, I didn't realise there were two.
> What would be your recommendation for getting that file deployed with > 'False' set. I can't get users to change it themselves, but arguably I > could write a script that changed it.
> My ideal scenario would be when that file gets created it takes the 'parent' > value from the growl.exe.config. Is that possible at all?
> Many thanks - and sorry again, > Ned
> On Tue, Mar 20, 2012 at 2:16 AM, Brian Dunnington > <briandunning...@gmail.com> wrote:
>> Last call for more info on this. I am planning to put out a new build >> very soon and would like to include the fix for this if it is still an >> issue for you, but I was unable to reproduce it when I actually tried >> to debug it. If you are editing the growl.exe.config file, that is the >> cause of the issue (the settings are read from each individual user's >> user.config file in their %LOCALAPPDATA% location instead).
>> On Fri, Mar 9, 2012 at 8:54 AM, Brian Dunnington >> <briandunning...@gmail.com> wrote: >> > Just out of curiosity, when you say you modified your config file, >> > what is the file location and name of the file you are editing?
>> > I did some more testing this morning to make sure I had found the root >> > cause, but I think I misspoke earlier when I said that Growl still >> > does one check upon launch even if AutomaticallyCheckForUpdates is set >> > to false. It does *not* seem to do that when I debug it and step >> > through the code, so I want to be sure that I understand how you are >> > approaching it so I can duplicate your behavior before I change >> > anything.
>> > On Wed, Mar 7, 2012 at 4:51 PM, Ned Lowe <ned.l...@gmail.com> wrote: >> >> Hi Brian,
>> >> Any update on this? The use case is that in the place where I deploy >> >> Growl For Windows, the users are pretty locked down - and so can't >> >> install anything. This means the popup they get when new versions are >> >> released is pretty annoying to them.
>> >> Many thanks, >> >> Ned
>> >> On Feb 17, 10:46 am, Ned Lowe <ned.l...@gmail.com> wrote: >> >>> Thanks Brian - that's much appreciated. Please let me know if/when >> >>> this can >> >>> be changed.
>> >>> On Tue, Feb 14, 2012 at 1:47 AM, Brian Dunnington >> >>> <briandunning...@gmail.com
>> >>> > wrote: >> >>> > You are not crazy - I just checked everything again and found the >> >>> > source of the trouble. Growl does use and honor the >> >>> > AutomaticallyCheckForUpdates setting, but only *after* the initial >> >>> > check at startup. So right now, it always checks when you first >> >>> > launch >> >>> > the app, and normally, would then check every 24 hours thereafter. >> >>> > If >> >>> > you set AutomaticallyCheckForUpdates to false, it wont keep checking >> >>> > every 24 hours, but it still does the initial check.
>> >>> > I dont remember exactly why I set it up that way, but at least it >> >>> > all >> >>> > makes sense now as to why it was still checking. I will take a look >> >>> > back through my release notes and see if there is any reason why I >> >>> > left it working that way or not.
>> >>> > Thanks for sticking with this and helping me find the root cause.
>> >>> > On Sun, Feb 12, 2012 at 11:10 PM, Ned Lowe <ned.l...@gmail.com> >> >>> > wrote: >> >>> > > Hi,
>> >>> > > I've checked and double-checked, I definitely have the following >> >>> > > in my >> >>> > > config file:
>> >>> > > But when Growl loads, it asks me to update (after about 10 >> >>> > > seconds).
>> >>> > > I'm running Growl 2.0.6.1 (I haven't updated deliberately so I can >> >>> > > check the behaviour).
>> >>> > > Thanks, >> >>> > > Ned
>> >>> > > (sorry for the cutoff message before)
>> >>> > > On Jan 26, 1:22 am, Brian Dunnington <briandunning...@gmail.com> >> >>> > > wrote: >> >>> > >> Growl for Windows does use and respect the >> >>> > >> AutomaticallyCheckForUpdates setting. To manually modify it, you >> >>> > >> have >> >>> > >> to make sure Growl is not running at all, then modify the file >> >>> > >> and >> >>> > >> save it, then re-launch Growl.
>> >>> > >> On Mon, Jan 16, 2012 at 7:55 AM, Ned Lowe <ned.l...@gmail.com> >> >>> > >> wrote: >> >>> > >> > Hi,
>> >>> > >> > I would like to prevent my Growl For Windows installation from >> >>> > >> > automatically checking for updates. Unlike the original Mac >> >>> > >> > version, >> >>> > >> > I cannot see a UI option for this, but the config file does >> >>> > >> > have >> >>> > >> > "AutomaticallyCheckForUpdates". I manually set this to False, >> >>> > >> > but I >> >>> > >> > still get the prompt after restarting everything.
>> >>> > >> > Am I doing something really stupid, or does Growl For Windows >> >>> > >> > not >> >>> > >> > respect this setting?
>> >>> > >> > Thanks, >> >>> > >> > Ned
>> >>> > >> > -- >> >>> > >> > You received this message because you are subscribed to the >> >>> > >> > Google >> >>> > Groups "growl for windows" group. >> >>> > >> > To post to this group, send email to >> >>> > growl-for-windows@googlegroups.com. >> >>> > >> > To unsubscribe from this group, send email to >> >>> > growl-for-windows+unsubscribe@googlegroups.com. >> >>> > >> > For more options, visit this group athttp:// >> >>> > groups.google.com/group/growl-for-windows?hl=en.
>> >>> > > -- >> >>> > > You received this message because you are subscribed to the Google >> >>> > Groups "growl for windows" group. >> >>> > > To post to this group, send email to >> >>> > > growl-for-windows@googlegroups.com. >> >>> > > To unsubscribe from this group, send email to >> >>> > growl-for-windows+unsubscribe@googlegroups.com. >> >>> > > For more options, visit this group at >> >>> >http://groups.google.com/group/growl-for-windows?hl=en.
>> >>> > -- >> >>> > You received this message because you are subscribed to the Google >> >>> > Groups >> >>> > "growl for windows" group. >> >>> > To post to this group, send email to >> >>> > growl-for-windows@googlegroups.com. >> >>> > To unsubscribe from this group, send email to >> >>> > growl-for-windows+unsubscribe@googlegroups.com. >> >>> > For more options, visit this group at >> >>> >http://groups.google.com/group/growl-for-windows?hl=en.
>> >> -- >> >> You received this message because you are subscribed to the Google >> >> Groups "growl for windows" group. >> >> To post to this group, send email to >> >> growl-for-windows@googlegroups.com. >> >> To unsubscribe from this group, send email to >> >> growl-for-windows+unsubscribe@googlegroups.com. >> >> For more options, visit this group at >> >> http://groups.google.com/group/growl-for-windows?hl=en.
>> -- >> You received this message because you are subscribed to the Google Groups >> "growl for windows" group. >> To post to this group, send email to growl-for-windows@googlegroups.com. >> To unsubscribe from this group, send email to >> growl-for-windows+unsubscribe@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/growl-for-windows?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "growl for windows" group. > To post to this group, send email to growl-for-windows@googlegroups.com. > To unsubscribe from this group, send email to > growl-for-windows+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/growl-for-windows?hl=en.
On Friday, March 23, 2012, Brian Dunnington wrote: > No worries - glad we got to the root of the problem.
> Up until v2.0.9 (just released yesterday), there was a bug that > prevented the default values in growl.exe.config from being used. That > bug has been fixed though, so you should be able to achieve your > scenario now. If you edit the growl.exe.config file, those values will > be used for each *new* user on the machine. So if a user has not run > Growl before (which, if you just installed it, should be the case), > then when they first run it, Growl will create the user.config file, > copying the growl.exe.config values. Note that if a user has already > ran Growl and their user.config already exists, then editing the > growl.exe.config will have no effect for that user.
> Try that out and let me know if that works for what you are doing.
> - brian
> On Wed, Mar 21, 2012 at 10:54 PM, Ned Lowe <ned.l...@gmail.com> wrote: > > Very sorry Brian - no idea how I managed to miss TWO mails from you. My > > sincere apologies - I don't use gmail for anything except this group.
> > OK - yes I was editing the growl.exe.config file bundled with the main > exe.
> > We don't have %LOCALAPPDATA% (just %APPDATA%), but we do have the Local > > AppData registry key. I checked the folder specified by that key - and > sure > > enough, there is a Growl folder, including a config file with > > CheckForUpdates set to True. Apologies, I didn't realise there were two.
> > What would be your recommendation for getting that file deployed with > > 'False' set. I can't get users to change it themselves, but arguably I > > could write a script that changed it.
> > My ideal scenario would be when that file gets created it takes the > 'parent' > > value from the growl.exe.config. Is that possible at all?
> > Many thanks - and sorry again, > > Ned
> > On Tue, Mar 20, 2012 at 2:16 AM, Brian Dunnington > > <briandunning...@gmail.com> wrote:
> >> Last call for more info on this. I am planning to put out a new build > >> very soon and would like to include the fix for this if it is still an > >> issue for you, but I was unable to reproduce it when I actually tried > >> to debug it. If you are editing the growl.exe.config file, that is the > >> cause of the issue (the settings are read from each individual user's > >> user.config file in their %LOCALAPPDATA% location instead).
> >> On Fri, Mar 9, 2012 at 8:54 AM, Brian Dunnington > >> <briandunning...@gmail.com> wrote: > >> > Just out of curiosity, when you say you modified your config file, > >> > what is the file location and name of the file you are editing?
> >> > I did some more testing this morning to make sure I had found the root > >> > cause, but I think I misspoke earlier when I said that Growl still > >> > does one check upon launch even if AutomaticallyCheckForUpdates is set > >> > to false. It does *not* seem to do that when I debug it and step > >> > through the code, so I want to be sure that I understand how you are > >> > approaching it so I can duplicate your behavior before I change > >> > anything.
> >> > On Wed, Mar 7, 2012 at 4:51 PM, Ned Lowe <ned.l...@gmail.com> wrote: > >> >> Hi Brian,
> >> >> Any update on this? The use case is that in the place where I deploy > >> >> Growl For Windows, the users are pretty locked down - and so can't > >> >> install anything. This means the popup they get when new versions are > >> >> released is pretty annoying to them.
> >> >> Many thanks, > >> >> Ned
> >> >> On Feb 17, 10:46 am, Ned Lowe <ned.l...@gmail.com> wrote: > >> >>> Thanks Brian - that's much appreciated. Please let me know if/when > >> >>> this can > >> >>> be changed.
> >> >>> On Tue, Feb 14, 2012 at 1:47 AM, Brian Dunnington > >> >>> <briandunning...@gmail.com
> >> >>> > wrote: > >> >>> > You are not crazy - I just checked everything again and found the > >> >>> > source of the trouble. Growl does use and honor the > >> >>> > AutomaticallyCheckForUpdates setting, but only *after* the initial > >> >>> > check at startup. So right now, it always checks when you first > >> >>> > launch > >> >>> > the app, and normally, would then check every 24 hours thereafter. > >> >>> > If
