iPad app and bluetooth keyboard

Craig Spofford
Craig Spofford Member Posts: 8
edited November 21 in English Forum

Hi - 

I have been trying to solve a couple of things with using notes and mobile logos for iOS.  

I was asked to attach logs so I did.  I have sent logs with this issue before via email, but was asked to post them here.

I am running an iPad air with iOS 10.0.1.  Currently I am using a logitech Bluetooth keyboard, but have also experienced this consistently with an apple bluetooth keyboard as well.  

My logos version is 5.5.5

Here's the two problems I have with the keyboard interaction.  

For clarity, I have had these issues for three plus years and have tried to report them.  The issue is not connectivity.  That has been ruled out.  

1. Auto correct.  When I type I make mistakes....  (blush).   If I key back to correct a mistyped word in notes in logos (doesn't happen in any other app) the autocorrect does not keep up so to speak and will start suggesting incorrect words.  For example.  I just typed example but started with exap.  I back space to change to m and then I am good in this forum.  In notes when I backspace it thinks I am on a new word and autocorrects to completely strange words. 

2. Tab key In notes.  When you open a note you can add a heading and then you can enter more info in the body of the note.  If you use the tab key to jump from the header to the body you get response in that you can type, but there is no cursor, and the note will not scroll down.  While you can type, when you fill that note screen it does not scroll to allow more.  However, if you touch the body of the note you both get a cursor and a responsive screen.  I'd think it should work the same whether you use the tab key or not since both ways direct you to the body of the note.  

I always use logos in landscape when studying, and almost always have split screen.  But whether this is a pop up note or a new document or if I am in split screen or not the result is the same.

Copy and  paste of scripture to notes is also not as good as into other apps because the footnote letters remain (although not active links) and that does not happen when going to another app.  This is not keyboard related though.

I really like using the keyboard, and this would greatly enhance the user experience if these issues worked.

Thanks for your help.

Craig

5280.info.zip

Tagged:

Comments

  • Kevin Byford (Faithlife)
    Kevin Byford (Faithlife) Member, Logos Employee Posts: 4,309

    Hi Craig,

    Thanks for posting here. We are already aware of the Auto Correct and Tab issues when using bluetooth keyboards but I don't have a time frame for when they might be fixed. I will reply to this thread again if there are any updates.

    Copy and  paste of scripture to notes is also not as good as into other apps because the footnote letters remain (although not active links) and that does not happen when going to another app.  This is not keyboard related though.

    There is already a case for this issue as well. 

  • Craig Spofford
    Craig Spofford Member Posts: 8

    I am happy to hear that this is at least a known issue.  In all of the times I have tried to report this before today no one acknowledged that.  I have been asking for that very confirmation - that I am not working with broken equipment - for at least three years.  

    I hope it can be accomplished at some point.  I prefer to use my iPad when not in the office and always use my keyboard when typing.  

  • Kevin Byford (Faithlife)
    Kevin Byford (Faithlife) Member, Logos Employee Posts: 4,309

    I am happy to hear that this is at least a known issue.  In all of the times I have tried to report this before today no one acknowledged that.  I have been asking for that very confirmation - that I am not working with broken equipment - for at least three years.  

    This is precisely why I requested that our Customer Support team send you to the iPhone/iPad Apps forum, so I could directly respond to you and that others who may be seeing the same issue can view this thread. Since your issues didn't crash the apps or cause data loss, etc. they are automatically of a lower priority from a support standpoint, and the number of customers using keyboards with our mobile apps are quite few (I am aware of only four customers, including you, although I'm sure there are others). 

    In any case I'll try to elevate this issue and hopefully we'll get a fix in sooner rather than later.