Why is Logos slowly killing its intuitiveness?

Jonathan Yap
Jonathan Yap Member Posts: 74
edited November 21 in English Forum

For the longest time, we just enter a reference in the box, hit Enter and then voila. Now we have to press Down also. What possible good does this change give?

Tagged:

Comments

  • Jonathan Yap
    Jonathan Yap Member Posts: 74

    I am glad this was resolved. https://community.logos.com/forums/p/220431/1283014.aspx#1283014

    Credit there.

    But this is another step back..

  • Rosie Perera
    Rosie Perera Member Posts: 26,202 ✭✭✭✭✭

    I'm not able to reproduce that. Can you confirm a few things for me?

    Version of Logos -- from About Logos which you can bring up from the three dots menu in the lower left corner.

    Windows or Mac?

    What Bible version? (I'm thinking it's NKJV -- I did a search on some of the text I see there.)

    What display settings do you have on in your Visual Filter menu (the icon with the three intersecting circles to the right of where you type in the verse reference).

    Could you click on that icon and take a screenshot of the menu that drops down and post it here?

    Thanks.

  • Jonathan Yap
    Jonathan Yap Member Posts: 74

    With more experimentation I realized it was a 1 out of 10 times thing. Apologies for overreaction. I cannot nail down why sometimes an input like Tab+"col 2"+enter fails to register and bring me to Colossians 2. I think it is a speed thing but it Cannot be my hardware (m1 mac). 

    but the issue still somewhat stands because I never had this problem in the past 10 years. 

    let me see how it goes 

  • Jonathan Yap
    Jonathan Yap Member Posts: 74

    My experiment is this. quickly tab+col 2+enter and then tab+rev 2+enter and rinse and repeat. In the past, it will switch seamlessly between col 2 and rev 2. Now, for me, some inputs fail to register.

  • Rosie Perera
    Rosie Perera Member Posts: 26,202 ✭✭✭✭✭

    My experiment is this. quickly tab+col 2+enter and then tab+rev 2+enter and rinse and repeat. In the past, it will switch seamlessly between col 2 and rev 2. Now, for me, some inputs fail to register.

    OK, I tried it a bunch of times, and one time it failed to register, but I realized I'd had a typo (I'd typed "cole 2") and that typo disappeared pretty quickly (I just barely managed to catch it out of the corner of my eye) as soon as I hit "Enter" and my Bible was left at Revelation 2.

    Is it possible that the times it failed for you, you were typing so quickly that you made a typo by mistake?

  • Sean
    Sean Member Posts: 1,761 ✭✭✭

    I had this happen multiple times in the recent past, though it doesn't seem to be doing it now. I also have not updated to Logos 31 yet. (I'm on Windows.)

  • Jonathan Yap
    Jonathan Yap Member Posts: 74

    No typos. It seems like the first instance you type a passage after a while it does not register. But subsequent instances right after are fine… 

  • Andrew Batishko
    Andrew Batishko Member, Logos Employee Posts: 5,362

    We have seen instances of this problem. We have a case open, but have had difficulties getting this to consistently reproduce. I added a link to this thread in the case so that we can post an update in the event that a fix is made.

    Andrew Batishko | Logos software developer

  • David McClister
    David McClister Member Posts: 106 ✭✭

    Having this same kind of problem as well. Logos does not always recognize a proper book-chapter-and-verse request for me.

  • David Paul
    David Paul Member Posts: 6,003 ✭✭✭

    "Slowly"??

    ASUS  ProArt x570s Creator, AMD R9 5950x, HyperX 64gb 3600 RAM, ASUS Strix RTX 2080 ti

    "The Unbelievable Work...believe it or not."  Little children...Biblical prophecy is not Christianity's friend.

  • Dave Hooton
    Dave Hooton Member, MVP Posts: 35,672 ✭✭✭

    Having this same kind of problem as well. Logos does not always recognize a proper book-chapter-and-verse request for me.

    Please clarify this issue in a new thread. State versions of the software you use and provide a screenshot or detailed example.

    Dave
    ===

    Windows 11 & Android 13

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

    Why is Logos slowly killing its intuitiveness?

    A serious answer to this question - an answer all users need to keep in mind. Because the userbase is changing rapidly in their expectations and in what they consider intuitive. My generation grew up with computers using tubes, taking up gymnasium sized spaces, and programming by wiring the machine. My son's generation grew up with green/black CRT tubes and programming in Basic ... games were very basic and not visual. My eldest grandson grew up with Dad's constantly tinkering with their computers - hardware and software, mice, game pads, color .. My youngest grandson grew up knowing how to use an iPad before he learned how to talk. Each of the four groups had expectations as to what would happen on particular keystrokes, mouse motions, selection, gestures ... each set of expectations based on the kinds of applications available at the time they were mastering the computer interface. On the iPhone I had a terrible time learning to flip to close a window ... tap and swipe I could grasp but flip? The younger generations find it hilarious that Grandma has trouble with such a basic gesture. Logos is built trying to find a middle ground among all users ... but as my generation ages, our expectations will carry less and less weight and the younger groups' expectations will carry more and more weight.

    So why is Logos slowly killing its intuitiveness from your perspective? Because you are aging and more and more of the userbase is younger than you with different expectations for intuitive.

    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."

  • scooter
    scooter Member Posts: 1,041 ✭✭

    A serious answer to this question

    Your statement is profoundly wise, MJ.  Thanks for taking the time to write this.