YAD

Richard DeRuiter said:

George Somsel said:

I went to bed last night (really, I did) having completed another download and re-indexing.  I woke this AM to find that I was getting another download. 

George, there have been three program updates (Beta 5, plus two updates - as I counted them), and three resource downloads in the last two days. The last one got to me yesterday afternoon (well, that's when I restarted L4 and was notified that there was an update pending). Each time, reindexing was required, unless it was interrupted by a new resource download. Usually the only way for L4 to know there was a new download/update was by restarting the program.

This has been a heavy week for downloading and reindexing. But I see this as part of the Beta process, as things get ironed out, resources tweaked, or in one case, forgotten then added, etc. Once L4 goes live, this should not happen nearly as frequently. But for now, it must, if we are to test what they've gotten so far.

Hi Rich,

             I hear you and i appreciate what you are saying but this indexing and re-indexing stuff is getting THREE much.

Ted.

George Somsel said:

<Y>et
<A>nother
<D>ownload

We have continually asked for better control over downloads because we want to:-

• mange re-indexing
• mange our download budget to the appropriate part of the month
• mange the content & effectively reduce total download

So far we have not seen any effective measures and we cannot even cancel an unwanted download (see Beta 5 Release Notes). Frankly, I don't want the Biblical Places, Biblical Things download (400 MB+) until the developers stop mucking around with the format and ASSURE us that this is stable. There are other downloads that apparently will not cause re-indexing from Beta 6, but we need to have these parceled so that we know the content and whether indexing will be necessary. And have better control over indexing than pausing for 4 hours (this is quite effective to permit outstanding downloads to complete but then you have to wait for the 4 hours to elapse!).

At the moment it is good policy to wait at least 2 days from a software enhancement to allow the developers to fix the missing bits, but we are then presented with a single large download (at the completion of which you change Program Settings to pevent further downloads!!).

If you have two machines you can save downloading by making the contents of the Resource folder available to the other machine (using Scan <folder>). But you may have a problem just restricting the machine to the software update. So I'm requesting that a link to the software update always be provided in the Beta Release Notes.

Todd Phillips said:

I agree with the better control part.  But I don't understand the "wait for 4 hours to elapse":  you can restart the indexing anytime you want by clicking on resume.

Thanks, Todd. I must have missed that!

Damian McGrath said:

BUG.....

The problem with Auto = No is that it queues that (old) download. It doesn't seem to reset to the current state and only perform the software update + single large update. We can't cancel the download and presumably issue Update Now to get back on track. Lack of user control again. So I figured my own way to do it!