Trying to update to 118. Have tried multiple times and have never been able to get more than 15% download before things stop. When they stop, I am unable to cancel or close the download pop-up and have to open Task Manager and close Java to shut down YAAC.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Disregard. Waited a couple hours and tried again and it went OK. A couple slowdowns where I though it might stall out again, but it finally completely downloaded.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hmmm... at what particular time were you doing that? On Thursday, I was downloading the latest whole-planet OpenStreetMap dataset, which clogs my network link for about 5 hours. All day Friday I was running the import of that dataset, which really beats my computer's disk drives into the ground, and therefore might have slowed down transmissions.
In any case, I will look into making the progress dialog's Cancel button more responsive. The present implementation only checks if the button is pushed when the status is updated, so if the long-running operation is stuck, it won't make any updates to have an opportunity to check for cancel.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Trying to update to 118. Have tried multiple times and have never been able to get more than 15% download before things stop. When they stop, I am unable to cancel or close the download pop-up and have to open Task Manager and close Java to shut down YAAC.
Disregard. Waited a couple hours and tried again and it went OK. A couple slowdowns where I though it might stall out again, but it finally completely downloaded.
Hmmm... at what particular time were you doing that? On Thursday, I was downloading the latest whole-planet OpenStreetMap dataset, which clogs my network link for about 5 hours. All day Friday I was running the import of that dataset, which really beats my computer's disk drives into the ground, and therefore might have slowed down transmissions.
In any case, I will look into making the progress dialog's Cancel button more responsive. The present implementation only checks if the button is pushed when the status is updated, so if the long-running operation is stuck, it won't make any updates to have an opportunity to check for cancel.