wjstarckI have an unusual problem that I'm not sure how to resolve.
I have AutomaticUpdater installed and working on a form. I have a menu item "Check for updates" that works flawlessly. However, I want also want updates to install automatically in the background, and this works...mostly.
My program is a plugin for another program. That other program launches maximized by default. If I launch my program with the other program's window maximized, AutomaticUpdater will initiate a download and install, but then the spinning wheel just sits there indefinitely. However, if I demaximize the host program's window first, then launch my plugin, everything works as advertised.
Any suggestions?
At what step is the infinite spinning icon happening? After your user click "Install update now"?
If this is the case, then the AutomaticUpdater is trying to shut down your program, but is unable to because Application.Exit() isn't killing the parent process.
You mention 2 apps - is your app a separate exe or is it a plugin to another host exe?
wjstarckAt what step is the infinite spinning icon happening? After your user click "Install update now"?
No.
My user can click "Check for updates" (scenario A) and that all works as expected, whether the host form is starts off maximized or not. My form is a plugin, launched from the host form. Consequently, I don't have any control over the host form (which always launches maximized).
In addition to having a "Check for updates" menu item, I also set the automaticUpdater control so that it will automatically check for updates when the form is launched (Scenario B, i.e., without user intervention). This is what I am having a problem with.
Scenario A always works, whether the host form is maximized or not. Scenario B only works if the host form has been unmaximized first. If the host form is maximized when I launch my form, and it tries to autoUpdate, I get the infinite spinning icon. I hope I have explained what's going on clearly 😉
You mention 2 apps - is your app a separate exe or is it a plugin to another host exe?
Plugin to another host.exe.
Thanks.
wjstarckWell that's strange.
I uploaded a new build of my plugin, and the problem seems to have gone away - maybe there was a solar flare or something :p
I'll let you know if the symptoms return. ❓
Well that's strange.
I uploaded a new build of my plugin, and the problem seems to have gone away - maybe there was a solar flare or something :p
wyBuild: now with sunscreen. 😉
I'll let you know if the symptoms return. ❓
Ok.
wjstarckOh... and one more thing.
Currently, if I set automaticUpdater as I have, so that no user intervention is required on update checking, is it possible to *always* have the "You already have the latest version installed" and green checkmark display after the form loads and aU has checked for updates?
Currently, if no update is available, nothing shows in the notification area. Seems like it would be more consistent if the green checkmark and message always show. Is this possible?
Thanks
Oh... and one more thing.
Currently, if I set automaticUpdater as I have, so that no user intervention is required on update checking, is it possible to *always* have the "You already have the latest version installed" and green checkmark display after the form loads and aU has checked for updates?
Currently, if no update is available, nothing shows in the notification area. Seems like it would be more consistent if the green checkmark and message always show. Is this possible?
Thanks
Let me explain our thinking. The focus is always your application. Your app's the star of the show - the AutomaticUpdater is just the assistant. If the check mark was ever-present then it would distract the user's eyes from your app.
The reason the check mark shows when the user manually checks for updates is that they need a response for their question. By clicking the "Check for updates" menu they're asking "Is there a newer version?". And the automatic updater has to respond either "yes" (the gold star icon) or "no" (the check mark).
However, when the automatic updater automatically checks, then it should only bother the user if there's something they can actually do. The check mark will quickly become meaningless if it's a constant presence or it pops-up seemingly out of nowhere (from the user's perspective).
Think of it like this: new versions of your app are special events. They're like birthdays.
If we start sending balloons to our user every weekday then it will make the birthday less special.
That being said, if you want to show the green checkmark every time the automatic updater checks and comes up with nothing, then I'll gladly explain it to you.
But have I convinced you of our way of thinking?
wjstarckThere's always gotta be one troublemaker, doesn't there 😈
I actually hadn't thought of it in those terms, and you make some excellent points. On the other hand, I actually like having a quicky visual confimation that I'm running the "latest and greatest". And if I'm not, I kinda get antsy...
So go ahead an humor me 😳
There's always gotta be one troublemaker, doesn't there 😈
I'm not saying this to give you a hard time. I genuinely want you to be successful, and I believe one step in that direction is to only bother the user when there is something for them to do. This way their focus is entirely on your product.
So go ahead an humor me 😳
If you want to do this only for debugging purposes, use the "UpToDate" event to show a message box (or any other debugging method).
Now, if you truly want this to be visible to your users, then simple change the "Visible" property of the AutomaticUpdater control to "True".
