Bug: resource pane lags behind other linked resources

Michael Lane
Michael Lane Member Posts: 48 ✭✭
edited November 2024 in English Forum

This screen shot explains the issue:

This happens with all three Clause Analysis resources: OpenText, Lexham, and Cascadia.

I have a layout that has all three of these tabbed in the same resource pane. Only the top resource lags behind.

Comments

  • Thomas Ball
    Thomas Ball Member, Logos Employee Posts: 3,261

    Michael:

    I am unable to reproduce any lag that is not acceptable. When linking the ESV to a Clause resource (all three you mentioned) the response time after changing locations in the ESV was very quick. They did not move at the same time but there was not an over-abundant lag. Perhaps you could describe to me what you are doing to reproduce this and I can compare that to what I was doing. I was just linking the resources and moving the scroll bar within where I figured the New Testament books were in respects to the scroll bar. I even went into the Old Testament a few times and the only response from the Clause resources was to not budge, but upon moving the scroll bar back to the NT area it followed suit. Using the scroll bar on the clause resources provides the same result.

     

  • Michael Lane
    Michael Lane Member Posts: 48 ✭✭

    This is not a scrolling issue, and maybe 'lag' is not the best term.

    Rather than scroll through a resource, try typing a few references in the ESV resource pane.

    In my example I had entered Rom. 8:1, then 1 Cor. 11:1, then Eph. 2:5. As the linked resources all went to the next reference, the Clause resource stayed one reference behind.

    the only response from the Clause resources was to not budge, but upon moving the scroll bar back to the NT area it followed suit.

    Same for me. That is, the Clause resource is one passage behind after entering a new reference or in your case, it was the first reference you went to and so the Clause resource didn't move at all. Then, when I start scrolling in the ESV the Clause resource jumps to the entered reference and then starts scrolling slightly behind the ESV (this 'lag' is not the issue I'm addressing).

  • Thomas Ball
    Thomas Ball Member, Logos Employee Posts: 3,261

    This is not a scrolling issue, and maybe 'lag' is not the best term.

    Rather than scroll through a resource, try typing a few references in the ESV resource pane.

    In my example I had entered Rom. 8:1, then 1 Cor. 11:1, then Eph. 2:5. As the linked resources all went to the next reference, the Clause resource stayed one reference behind.

    the only response from the Clause resources was to not budge, but upon moving the scroll bar back to the NT area it followed suit.

    Same for me. That is, the Clause resource is one passage behind after entering a new reference or in your case, it was the first reference you went to and so the Clause resource didn't move at all. Then, when I start scrolling in the ESV the Clause resource jumps to the entered reference and then starts scrolling slightly behind the ESV (this 'lag' is not the issue I'm addressing).

    I'm sorry I am still unable to reproduce what you are experiencing. I think you misunderstood my statement you quoted. The reason it did not move (in the context of my statement) was because the Clause resource was a NT resource therefore when I moved the bible (ESV) to OT text the Clause resource would not follow. 

    In your image I see you have the NASB, was that linked to the other two resources? EIther way could you reproduce teh bug and post your logs? Instructions for doing that are linked from my signature below. Thank you.

     

  • Michael Lane
    Michael Lane Member Posts: 48 ✭✭

    Yes, NASB was linked with the ESV and the Clause Analysis. I closed the NASB so that I only had two resources open and the same thing happens.

    I went through a sequence of entering several references and the problem duplicates every time.

    I have only experienced this with the Clause resources.

    78307.Archive.zip

    It could always be the guy pushing the keys!