Thanks Stephane. If you are using a remote indiserver running on another computer, don't forget to update that too. There were some changes to INDI in the last couple of months. I forgot to update INDI on my raspberry pi and last night we had the first good clear night in ages. So I spent a significant chunk of good imaging time updating the software on the pi. If I had thought about it sooner, I could have easily done that in the daytime beforehand. . .
I set my systems to auto update. So far it's working great bar the odd crashes from time to time.
I had a crash while trying to set up the horizon limits earlier, nothing serious, a one off crash.
Thanks Rob,
I tested all new features and they're working well. I checked more in depth the new astrometry features by adding a new scope configuration (with a different FOV). the new optical features were recognized and new index files were recommended accordingly. Deleting files by unchecking them and lack of connectivity warning worked as well. Excellent work as usual.
Remember, some of them are actually quite a few files, and some of them are very big. The ones at the top should definitely download with no problem. the farther down you go, the longer it will take. I currently set a timeout for individual files of 1 minute, in case a download has a problem, but we will need to see if that is too short. If the index gets grayed out or disabled, that means it is trying to download. If it comes back and is NOT checked, that means it timed out.You could always try again. If there is no connection, it should not even try, i.e. if you check it, it should immediately uncheck and give you a warning that it cannot connect.
Looking at your screenshot, it appears you are downloading both 4207 and 4208. From my experiments, it seems to me that downloads wait until the other is finished. I had hoped that they would download simultaneously, not sequentially. If you are using the smaller files (the ones at the top), you can check them at the same time and it will not be an issue. But if you check more than one at the bottom at the same time, there is a good chance one will time out while waiting in "line". I might have to play around with the timeout feature. I think it is important in case a download never completes, but maybe it should be a longer time.
ah, I had not noticed the * in the file name... doh... that means several files are being downloaded. That explains why it seems slow.
I thought it was just one file.
Based on what you said, it might be good to include some where the number of files that will be downloaded. I at least think that it would be good to include the file sizes. See what you think about this screenshot. Does this help?