BUG: Parallel Resource Sets

JH
JH Member Posts: 801 ✭✭✭
edited November 20 in English Forum

Running Logos 6.8 SR-1 (OS X - 10.11.2)

1 - Look at a lemma in a lexicon (for example in HALOT)

2 - Click the Parallel Resource Sets icon and choose another lexicon

3 - Press the left history icon to go back to the original lexicon

4 - Click the Parallel Resource Sets icon again. I always get the following:

Comments

  • Dave Hooton
    Dave Hooton MVP Posts: 35,770

    I can't reproduce using my setup. Do you have a collection of lexicons that is used for Parallel Resources?  What Hebrew lexicons do you have e.g DBL Hebrew, Enhanced Strong's which I used?

    Dave
    ===

    Windows 11 & Android 13

  • Jack Caviness
    Jack Caviness MVP Posts: 13,514

    Had this problem appear randomly, but the more I experimented in attempting to isolate the but, the better Parallel Resources performed. Now, Parallel Resources seems to work pretty much as designed.

  • Reuben Helmuth
    Reuben Helmuth MVP Posts: 2,485

    I can reproduce this with almost 100% consistency. I started from 'lodged' in Joshua 3:1, selected HALOT from the context menu, chose TDOT from parallel resources, clicked back to HALOT, click on parallel resources>"No parallel resources." Note that when toggling back and forth between the two via the back/forward arrows for a couple times, the parallel resource button would once again bring up my PRs.

    What's more...occasionally I would get the "No parallel resources" message even on the first go (no need to navigate to another lexicon and return).

  • Dave Hooton
    Dave Hooton MVP Posts: 35,770

    Reuben, please respond to my questions. Also, enable logging and upload the zipped log folder when the error occurs.

    Dave
    ===

    Windows 11 & Android 13

  • fgh
    fgh Member Posts: 8,948 ✭✭✭

    I've had a large number of cases recently where I got 'No parallel resources' although I knew there should be such, so it could be a Mac issue. No time to investigate.

    Mac Pro (late 2013) OS 12.6.2

  • Andrew Batishko
    Andrew Batishko Member, Administrator, Community Manager, Logos Employee Posts: 5,395

    I can reproduce this with almost 100% consistency. I started from 'lodged' in Joshua 3:1, selected HALOT from the context menu, chose TDOT from parallel resources, clicked back to HALOT, click on parallel resources>"No parallel resources." Note that when toggling back and forth between the two via the back/forward arrows for a couple times, the parallel resource button would once again bring up my PRs.

    What's more...occasionally I would get the "No parallel resources" message even on the first go (no need to navigate to another lexicon and return).

    Reuben, thanks for these steps. I'm able to recreate the problem, and I've created a case to get this fixed.

    Andrew Batishko | Logos software developer

  • Jack Caviness
    Jack Caviness MVP Posts: 13,514

    Reuben, thanks for these steps. I'm able to recreate the problem, and I've created a case to get this fixed.

    Glad you could reproduce. For me, it is quite inconsistent, but it seems to occur the first time HALOT is accesses, especially when it is the host for a Multiple Resources window .

  • Andrew Batishko
    Andrew Batishko Member, Administrator, Community Manager, Logos Employee Posts: 5,395

    JH said:

    Running Logos 6.8 SR-1 (OS X - 10.11.2)

    1 - Look at a lemma in a lexicon (for example in HALOT)

    2 - Click the Parallel Resource Sets icon and choose another lexicon

    3 - Press the left history icon to go back to the original lexicon

    4 - Click the Parallel Resource Sets icon again. I always get the following:

    After your step 3, I think you can work around the problem by scrolling your resource up just a little to the previous word, then back down to the desired word before opening the Parallel Resource Sets list. If that gets around the problem then I've got a fix internally that will ship with an upcoming release.

    Andrew Batishko | Logos software developer

  • Angela Murashov
    Angela Murashov Member Posts: 1,532

    Reuben, thanks for these steps. I'm able to recreate the problem, and I've created a case to get this fixed.

    This should be fixed in 6.9 Beta 4.