BUG: Activate Text Field Focus in Copy Bible Verses Tool?
Hello again,
When activating the Copy Bible Verses tool using the keyboard shortcut on Mac, the cursor is not focused on the text field where one types the verse. The window pops up, but any keyboard stroke produces an error sound. One has to physically click the text field with the mouse before beginning to type.
Moreover, it looks like Logos 9 for Mac doesn't comply with MacOS's accessibility features of using the keyboard to change focus on text fields and buttons. Using the usual TAB or SHIFT+TAB in the Copy Bible Verses does nothing.
Is there a way to automatically focus on the text field for the Copy Bible Verses window? Alternatively, is there a keyboard shortcut to activate that text field?
Thank you kindly.
I use Verbum with an 8-Core Mac Pro (2013) and a MacBook Pro (2017)
Comments
-
FrMoses said:
When activating the Copy Bible Verses tool using the keyboard shortcut on Mac, the cursor is not focused on the text field
Does that apply to Opt+Cmd+B or Shift+Cmd+J ?
Dave
===Windows 11 & Android 13
0 -
Yes, on my Mac, I use the standard shortcut, SHIFT+CMD+J. The CBV window opens, but it's unusable until I manually click on the text field to type a reference. I wish it was ready to go when activated.
I use Verbum with an 8-Core Mac Pro (2013) and a MacBook Pro (2017)
0 -
Do you get the same result with the other shortcut?
Dave
===Windows 11 & Android 13
0 -
The other shortcut doesn’t do anything on my Mac.
What happens when you activate this window? Is the cursor in the text box ready to go? Maybe that will tell us if this is isolated on my computer or a general UI issue.
I use Verbum with an 8-Core Mac Pro (2013) and a MacBook Pro (2017)
0 -
FrMoses said:
What happens when you activate this window? Is the cursor in the text box ready to go?
It works in Windows (CTRL+Alt+B) as I can begin typing a new passage. It is the same when opening from the Tools menu.
It looks like a Mac issue, and not an isolated one.
Dave
===Windows 11 & Android 13
0 -
That’s really interesting. I think there should be parity between the two versions in something as basic as this.
I will try to update the title to reflect that this is an apparent bug.
I use Verbum with an 8-Core Mac Pro (2013) and a MacBook Pro (2017)
0
