AU: Only show newversion message on initial checkingSolved

I'll look into this -- I'll get back to you.

Thank you, Sam!

Btw, if this behaviour is by design and you decide to not change it I could tweak this on my own if you tell me what to change - since I'm already making a custom build of the AU control to integrate custom icon.

The KeepHidden property was broken in our massive backend rewrite that happened in version 2.6.11. We'll fix this for the next version (we're shooting for a Friday release).

Glad to hear that! Looking forward to the next release. 🙂Thank you very much for the great support!

Andreas

wyBuild 2.6.12 is now out -- this "KeepHidden" bug has been fixed.

Hey Wyatt, hey Sam,

Thank you for the quick update and the excellent support.

But somehow I'm still facing the same issue. I must be doing something wrong...

- Initially the AU control's UpdateType is set to "DoNothing".- In the form's constructor I call a method which translates the AU strings.- In the form's load event I call a method that checks the application settings (stored in a database) and sets the control's UpdateType property to either "Automatic" or "DoNothing" according to the user's preferences.- WaitBeforeCheckSecs is set to "10" (default); so after all the initialization stuff and after the 10 seconds the Updater checks for updates. But not silently ...

Also setting KeepHidden to "true" has still no effect. As I said, I must be doing something wrong because I don't think you say you fixed the issue when actually nothing happend.

I try to reproduce this in a sample app and send you the code.

Kind regards,Andreas

Sent two sample projects where I get the described error to 'support@wyday.com'. Hope that helps. 🙂

You need to set Visible to false and KeepHidden to true. In the examples you do neither.

Humph. Okay, I'll try that tomorrow at work.What I'm wondering about is that at no time I altered these two properties in my application (I kept the default setting) and in the previous versions (as described in the first post) everything worked fine (respectively, it worked as I expected it to work).But if the current behavior is by design and it's "fixable" through this two properties than this is fine to me, too. 🙂

Thanks so far!

Ok, I have now set KeepHidden to true and Visible to false. Now, when the application starts, the user doesn't get notified on errors or when he already is up-to-date.In the ReadyToBeInstalled event I set the control visible, so the user knows he can install an update. Also when he manually clicks on Check Updates I set KeepHidden to false and Visible to true.

Now one drawback with the current solution that I encountered is when the user installed an update and the application is being restarted by the updater the update-success message is not shown because the control is not visible by default. I guess setting the control to visble in the UpdateSuccessful event should solve this?

I'm not sure what you're trying to do. KeepHidden keeps the AutomaticUpdater control hidden -- that is, use this property if you want to display your own UI.

Why don't you just use the default visibility of the AutomaticUpdater? It only shows itself when it's doing work or it has something to say to the user.

I try to clarify. Maybe my English too bad?

I used the default visibility of the AutomaticUpdater since I integrated it in my application. What this thread is all about is that the default behaviour of the AU control has changed in one of the earlier release.

When I first used the AutomaticUpdater the behaviour was the following:- When the user started the application the updater *automatically* checked for updates in the background. The user didn't see that this background process was taking place. When the updater encountered an error it did not notify the user about this error. When the user already had the latest version the updater did not notify the user about that. When the updater found an update it downloaded the files (invisible to the user) and when the download succeeded the updater popped up and informed the user "Update will be installed on next application start".- When the user *manually* checked for updates he was informed about every step taking place: He saw the waiting circle animation when the updater was searching for or downloading new updates. When an error occured he saw the red cross, so that he knew an error occured. When he already had the latest version he saw the green tick, so that he knew he is already up-to-date.

The currect behaviour of the AutomaticUpdater is the following:- When the user starts the application the updater automatically checks for updates. But, in contrast to the old behaviour, everything happens visible to the user. He sees the waiting circle while the updater searches for new version, he gets informed about errors and when he already is up-to-date. So most of the time the user starts the application he sees the message "you are already using the latest version". Well, that's nice for the user, but it's iritating to him because he didn't request the program to search for updates and therefor doesn't expect a notification about the program's update state.

In my first post I only mentioned the KeepHidden property because I thought i could maybe mimic the previous behaviour. Which I now can, but which is not what I was after, originally.

Hope I was able to clarify some misunderstandings. 😉

Yes, this makes sense. I'll look into reproducing this bug tomorrow.

Thank to wyBuild I have a full working copy of every version of my program I released. 🙂So I can narrow down the issue to somewhere between the AutomaticUpdater version 2.6.9 (*old* AU behaviour) and 2.6.11.2 (*new* AU behaviour).

Does this help?

This is fixed in the latest AutomaticUpdater -- out now with wyBuild 2.6.13

Yes, this works now. Thanks for the update!