Highlighting problem — frequently uses wrong anchor

Stuart S
Stuart S Member Posts: 48
edited November 21 in English Forum

I want my Bible highlights to show up in specific versions only. it gives me a fresh look as I read in a translation I have not read before.

The problem is some highlights change my selection to include the whole verse and not be specific to the translation (anchor includes verse reference only, instead of selected words and Bible version. This leads to other Bible versions having two-color highlights, the one specific to the translation and the one with the generic anchor. I tried reporting this as a bug, but haven’t heard anything back.

For information, I most often use natural highlight palette. Swipe to highlight is off, as is Smart Text Selection.

Help!

Stuart

Tagged:

Comments

  • JT (alabama24)
    JT (alabama24) Member, MVP Posts: 36,472 ✭✭✭

    Can you provide screenshots? 

    macOS, iOS & iPadOS | Logs |  Install

  • Ali Pope
    Ali Pope Member, Logos Employee Posts: 1,821

    Hi Stuart, this is a known issue and we have a case created for it. I will let you know when the issue has been resolved. Thank you for reporting!

    Ali Pope | Logos Desktop and Mobile Program Manager

  • Stuart S
    Stuart S Member Posts: 48

    Thank you! Was just about to post screenshots (thanks, JT). Eagerly awaiting correction!

  • Stuart S
    Stuart S Member Posts: 48

    Amy updates on this? Had hoped it was fixed with last update that mentioned highlighting fix, but the problem persists.

  • Ali Pope
    Ali Pope Member, Logos Employee Posts: 1,821

    After looking into your situation a little more, we've understood your report to actually be new/intended behavior for the L10 update. We have somewhat changed the highlighting logic for L10. It is as follows:

    • In L9, highlights were always anchored to text ranges, even if you selected an entire verse. So in L9, highlighting the verse John 1:1 in the NLT would only highlight the NLT.
    • In L10, we’ve change the selection paradigm a bit in Bibles. Tapping will select a verse. If you then add a highlight, that highlight will be anchored to the verse milestone, not the text range. So, in L10, if you tap to select John 1:1 and add a highlight in the NLT, that highlight will be visible in the NLT, the NIV, the ESV, etc. This was an intentional change.
    • In L10, you can still select a subset of the verse, and that highlight would be anchored to just that Bible (as a text range anchor).
    • In L10, if you manually select verse text and we determine that you have effectively highlighted the entire verse, a highlight will be applied to the verse in all bibles. You can tell the behavior by looking at the “context” in the selection menu. If it is a verse or verse range, the highlight will be anchored to these verses regardless of translation. If the context is just a preview of the text selected, the highlight will be applied to the text range in just that resource.

    So, all that to say, highlighting is different in L9 vs L10. These changes were intentional. As such, I’m not sure this is a bug, but is behaving as designed. If you are seeing a different behavior than what I have listed above, please let us know!

    Ali Pope | Logos Desktop and Mobile Program Manager

  • Stuart S
    Stuart S Member Posts: 48

    Why? I loved highlighting each Bible version separately. I have been doing the workaround you described, but it slows down and complicates the whole process. 

    I’m probably the only one that feels this way, but this falls in the “if it’s fixed, break it” category. It ruins the highlighting I have done for years by putting double highlights on verses, often in different colors.

    The behavior is not consistent in the mobile app. When I start selecting from the first letter (not the verse number) to the period, sometimes it uses the verse for the anchor, sometimes it uses the text range. So I would say there is a bug anyway.

    And this is not the behavior in the L10 desktop app. I can select the same way, starting with first letter (not verse number) through the period. The same verses default to whole verse in mobile, but use the text range in desktop app.

    Please reconsider this "feature." Or at a minimum add an option to toggle this behavior back to L9, in case there are any other users that this decision effects in such a devastating manner.

    Sincerely,

    Stuart


  • MJ. Smith
    MJ. Smith Member, MVP Posts: 53,059 ✭✭✭✭✭

    In L10, if you manually select verse text and we determine that you have effectively highlighted the entire verse, a highlight will be applied to the verse in all bibles. You can tell the behavior by looking at the “context” in the selection menu. If it is a verse or verse range, the highlight will be anchored to these verses regardless of translation. If the context is just a preview of the text selected, the highlight will be applied to the text range in just that resource.

    I don't use mobile but I would object to this change. I like to choose for myself if a note is on reference or selection ...it often has nothing to do with "full verse" (or multiple verse) -- it has to do with the content of the note applying to a particular translation or all translations.

    Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."