To immediately update to the current beta enter the Update Now command. Otherwise, the app will automatically update the next time it's scheduled to check for updates.
Release Notes
Mac
Windows
7.10.0.0018 is reporting no updates available 13th October 08:13 GMT
Sorry if I am intruding, but I didn't know where else to ask this.
In the new release coming shortly, I believe there was a note that any concordance search would be saved in the History tab. I'm wondering if it's at all possible to save it in a Documents file, or Guide, or something of that nature?
And does this mean that, once a book's concordance is compiled for the first time, that compilation will now be saved, and available again without re-compiling?
Thank you so much!
Paul L. White, Satisfied Logos User since 1.6
I'm wondering if it's at all possible to save it in a Documents file, or Guide, or something of that nature?
It's saved within the Concordance Tool itself - https://community.logos.com/forums/p/148264/928213.aspx#928213 - why would you want it in a Document, Guide?
Yes
Thank you, Mr. Criddle.
I guess I'm a little confused in that ... every single time ... I have opened the Concordance Tool it would redo the Concordance build. I have it set on NASB, and all passages, and Lemma.
The only thing I can think of is that NASB must have updated between the Concordance usages.
I don't have the option that is shown in the link you provided, so I'm presuming that will come with this new software update. And I'll presume that the discussion with Mark Ward was about the Beta version.
What I did was to take the History link (since I don't have a "Concordance History" option per se), and put it in my Favorites under a Folder "Concordances." But now, even choosing the Concordance Tool will bring up the already compiled version.
I tried closing the software, and opening again. And it was still compiled, again leaving me with the conclusion that NASB has been frequently updated.
I don't know if I should, but I never "clear" my history. So I couldn't find the last time I compiled, sorry. Think it was a couple of weeks ago.
So now, if NASB has already compiled, and an update comes, and I choose from my Favorites the Concordance to NASB, it will recompile on me, correct? If there's been no Update to that Bible, then no re-compiling will be necessary. Also correct? And the pin this Concordance option will be what is coming with the update?
Blessings to you for donating your time to us and answering what seem to be rather difficult questions.
Paul
PS The reason I wanted it in a document file was so I could pull up the Concordance without it recompiling. And, if you have several books compiled, then each one would be available individually...by name. Blessings.
I don't have the option that is shown in the link you provided, so I'm presuming that will come with this new software update
Yes - you will need the updated released for this functionality. Until then concordances are recompiled once the "cache" is full - effectively you can have 10 compiled ones (I think that's the number) and then when you open another resource one drops out. And when resources are updated the Concordance does need to be rebuilt
Thanks - appreciated
PS The reason I wanted it in a document file was so I could pull up the Concordance without it recompiling.
With 7.10, assuming you have "kept" a concordance it won't need to be recompiled unless the resource is updated
And, if you have several books compiled, then each one would be available individually...by name
You will be able to do this from within the Concordance Tool itself - from its History dropdown
every single time ... I have opened the Concordance Tool it would redo the Concordance build
This shouldn't happen — unless there has been an update, or unless you have generated many other Concordances in between (the tool is supposed to keep the last ten cached so they don't have to regenerate). The coming update simply allows you to 'pin' certain resources, so that they're never deleted from the cache.
If this is not the behaviour you're experiencing, then there's likely something wrong with your system. The best way to diagnose that would be to post logs.
The concordance for Bibles actually bring together several datasets. I think it's:
If only one of those gets updated, the Concordance will need to be regenerated.
Correct on all three counts.
This looks like a wonderful tool coming up, Mr. Criddle. Again, thank you so very much.
Mr. Barnes,
Bingo, Bingo! Once a month, at least one of those datasets gets updated. That's the reason, then, for the recompiling.
Thank you so much for adding those details. I hope they will be listed somewhere in documentation.
I think it's one of the most powerful reasons to have Logos is this constant updating. And recompiling a concordance once a month is a small price to pay for having up to date information.
I've enjoyed reading your posts for a long time now, and truly appreciate, as with Mr. Criddle, all of the time you put into supporting this software.
I honestly believe it's the best software product every produced. Even more splendid than any particular OS or word/number processor. It brings together so many formats in computer science, and utilizes every one of them for one purpose: to glorify God through His Word! Blessings to you and Mr. Criddle and Miss Philana, and all who work at Faithlife. You're in my daily prayers!
Mike,
Is this still an issue? I was able to update my copy of 7.10 RC 1 to 7.10 RC 2. Can you try to run the command Update Now?
7.10.0.0018 is reporting no updates available 13th October 08:13 GMT Mike, Is this still an issue? I was able to update my copy of 7.10 RC 1 to 7.10 RC 2. Can you try to run the command Update Now?
Hi Philana
I ran a 'Set update channel to Beta' command and the update started right away.
Not sure how that became unset though.
I have the same issue. I'm stuck on RC1. Update Now says no updates are available, but the Help/About screen gives the yellow dot next to the version number.
My log file says this:
2017-10-14 08:14:50.4034 3 Info UpdateManagerCallback Checking for updates from 'https://clientservices.logos.com/update/v1/feed/logos7/beta.xml'.2017-10-14 08:14:50.9611 3 Info UpdateManagerCallback Checking feed for application updates newer than version 7.10.0.18.2017-10-14 08:14:50.9631 3 Info UpdateManagerCallback Found application update (version 7.10.0.19).2017-10-14 08:14:51.2264 3 Info UpdateManager Current installer (version 7.10.0.19) has a status of Installed.
6403.Logos.log
I'm sure I could get it installed with a channel change or manual download, but I've left it like this in case you want to do further diagnosis.
