Comments Closed
truly welcome! indeed!
Peace to all!
Philippians 4: 4 Rejoice in the Lord always; again I will say, Rejoice. 5 Let your reasonableness be known to everyone. The Lord is at hand..........
But not necessarily accurate. On a Strong's Number in type:lexicons (19 resources) I'll get 12 resources of which half don't have an index! On another occasion I'll see 6 resources in Lexicons.
Can you provide some details or a screenshot?
Open DBL Greek and set the reference to G4033:-
Jump to Enhanced Strong's:-
Note 1. ESL initially showed the corresponding GK number, not the Strong's number.
2. If i jump back to DBL Greek it shows the same Lexicon list as ESL!
3. A similar case is G4100, but when it goes back to DBL Gk the list is the same 6 as ESL
4. It does not occur for all references in DBL Gk, nor is it repeatable for the ones I've shown here.
5. The story is the same for DBL Hebrew to ESL and back.
6. ESL can also give a verbose list & jumping to DBL provides the shorter list!
Dave
===
Windows 11 & Android 13
Open DBL Greek and set the reference to G4033:-
[snip]
OK, I see the problem here, but I'm pretty sure this is exactly how 4.1 behaved. (The optimisation only changed how the "All Parallel Resources" list was created, it didn't change how the list for a custom collection is created, what happens when you jump to a parallel resource, etc.) I'll file bugs on the issues you've raised.
4.2 beta 3 INSTANT parallel resources
Great news. Fast PRA's make working on notebooks (with their small displays) wonderful. Back in the L3 days, I learned the location of my frequently accessed resources, so checking them was as automatic as touch-typing. E.g. In a Bible window, from my default Bible, 2 left arrows was the NIV, 1 right arrow was HDNT, etc. It may sound strange, but I found it less "stressful" to check other resources this way than mousing and clicking on tabs.
Having been one of the biggest complainers about slow parallel resources, can I just say a very big thank you for quietly slipping out this improvement. Would you care to share what, technically you have done?
Some bugs do remain, however, seemingly with resources with an irregular coverage. For example, opening a commentary to 2 Corinthians 5:21 shows Harotounian's Calvin commentary whose index jumps about all over the place, and you just end up going to the title page.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
Having been one of the biggest complainers about slow parallel resources
Hi Mark,
I don't know if you are the biggest, I have been complaining about this too and I am 6' 6" tall which makes me bigger than 99% of the population.
I too am grateful that this feature finally works the way it should have from the beginning.
Thanks Logos.
Having been one of the biggest complainers about slow parallel resources, can I just say a very big thank you for quietly slipping out this improvement. Would you care to share what, technically you have done?
We started caching resource collections; collections are no longer re-evaluated every time the menu is dropped down. This will also help a lot for users with nested collections.
We also eliminated code that opens every resource in the "All Parallel Resources" collection and checks if it actually has the current reference; instead, we use metadata about the range of references that the resource contains to detect (much more quickly) if the resource is very likely to have the current reference. This logic was already being used for custom collections; we just extended it to All Parallel Resources.
Some bugs do remain, however, seemingly with resources with an irregular coverage. For example, opening a commentary to 2 Corinthians 5:21 shows Harotounian's Calvin commentary whose index jumps about all over the place, and you just end up going to the title page.
This is a result of the less precise (but much quicker) verification that is happening in Beta 3. You would have experienced exactly the same behaviour in Beta 2 if Calvin: Commentaries (Haroutunian) was in a custom collection; in Beta 3, it's also now happening in "All Parallel Resources".
This is a result of the less precise (but much quicker) verification that is happening in Beta 3. You would have experienced exactly the same behaviour in Beta 2 if Calvin: Commentaries (Haroutunian) was in a custom collection; in Beta 3, it's also now happening in "All Parallel Resources".
I'll take the compromise. Good choice in my book.
Thank you Logos for listening!
And thanks for the Last Updated field in the Library display.
Peter
Wow, missed that in the release notes. That might just change how I do things a bit....
Yes it is great.
As mentioned in the release notes, Headword resources are not faster. But could someone check to see if their collections are not working with Dictionaries, etc (Headword resources) when using Parallel resource button. Thanks.
EDIT: false alarm. Something broke in my rules for my dictionary collection.
QLinks, Bibl2, LLR, Macros
Dell Insp 17-5748, i5, 1.7 GHz, 8G RAM, win 8.1
This is amazing. Time for some optimizing on the Mac side. Well done!
Do you need to change "type:Dictionary" to "type:Encyclopedia"? http://community.logos.com/forums/t/24033.aspx
This is absolutely awesome!! I have been very critical of Logos on the parallel resource problem. But this is the best update so far. It makes Logos SOOOO much more usable.
Thanks!
Fred Greco
Senior Pastor, Christ Church PCA, Katy, TX
Windows 10 64-bit; Logos 7.1 SR-2 (Reformed Platinum)
Thank you Sir! That was exactly the problem. Guess i missed that post [:D]
QLinks, Bibl2, LLR, Macros
Dell Insp 17-5748, i5, 1.7 GHz, 8G RAM, win 8.1
I wouldn't say "INSTANT" (it took 2-3 seconds for me), but it's clearly much faster than it was before, and I'm sure it would be even snappier if I had a machine with better benchmarks. Thank you!
Is it 2-3 seconds every time you use the menu, or just the first time you drop it down? (The first time it's used it may take longer, particularly if you have many collections.)