Please put the focus on the first entry in a Library search

Right now I can type "cmd-l" on my Mac to bring up the Library pane. I type "na28" and it's at the top of the list, but since the focus isn't on it, I still have to use my mouse to select it. If the focus was on it, I could just hit return to open it.

Type na28 into the Command Box and the focus could well be on that bible, but wait for the list to generate first! However, what do you do when NA27 brings up 3 or more bibles?

Note that the Command Box can be trained, so if na28 does not bring the book into focus, select it and it should be the focus next time.

https://community.logos.com/discussion/comment/1309014#Comment_1309014

Right now I can type "cmd-l" on my Mac to bring up the Library pane. I type "na28" and it's at the top of the list, but since the focus isn't on it, I still have to use my mouse to select it. If the focus was on it, I could just hit return to open it.

Type na28 into the Command Box and the focus could well be on that bible, but wait for the list to generate first! However, what do you do when NA27 brings up 3 or more bibles?

Note that the Command Box can be trained, so if na28 does not bring the book into focus, select it and it should be the focus next time.

Usually the resource I'm looking for is at the top of the list. If it's not, I should be able to use the down-arrow to navigate to the resource I want, then hit return to open it. Right now, I can't do that. I always have to use the mouse at some point.

Jonathan Huber

https://community.logos.com/discussion/comment/1309018#Comment_1309018

Mark, try command box instead of library. Cmd+Opt+L. That's pretty cool, I need to remember to use command box more. Open NA28, Nahum in Factbook, search books for eucharist... those all work there. Thanks, Dave!

https://community.logos.com/discussion/comment/1309024#Comment_1309024

Mark, try command box instead of library. Cmd+Opt+L. That's pretty cool, I need to remember to use command box more. Open NA28, Nahum in Factbook, search books for eucharist... those all work there. Thanks, Dave!

Thanks Dave and Jonathan. I get it now :-) This will work just fine.

https://community.logos.com/discussion/comment/1309025#Comment_1309025

Thanks Dave and Jonathan. I get it now :-) This will work just fine.

Use https://wiki.logos.com/Desktop_Commands for the syntax that Jonathan hinted at e.g. open na28 to mt (open to Matthhew). It is flexible as open is not needed if just opening a book/bible like NA28.

John

https://community.logos.com/discussion/comment/1309090#Comment_1309090

Thanks Dave and Jonathan. I get it now :-) This will work just fine.

Use https://wiki.logos.com/Desktop_Commands for the syntax that Jonathan hinted at e.g. open na28 to mt (open to Matthhew). It is flexible as open is not needed if just opening a book/bible like NA28.

Is there a way to assign hotkeys to open your favorite resources?

Jonathan Huber

https://community.logos.com/discussion/comment/1309098#Comment_1309098

Is there a way to assign hotkeys to open your favorite resources?

Yes, you can assign up to 9 favorites. Open Favorites from Tools to see and set them up.

John

https://community.logos.com/discussion/comment/1309103#Comment_1309103

Yes, you can assign up to 9 favorites. Open Favorites from Tools to see and set them up.

It works [Y]

I tried it out on Windows. It will no doubt be similar on MacOS

You have to drag the window title and drop it on the "Set link 1", or alternately highlight the Window title bar of the favorite Resource and press Ctrl-Shift + 1 to assign that resource to key CTRL-1. (Red Circle 1)

Another option which I had already been using is to drag the windows title with the mouse and drop it on the Toolbar. You can then open the Resource with a single mouse click (so not really the answer to the question in this thread). (Red Circle 2)

https://community.logos.com/discussion/comment/1309149#Comment_1309149

It works

Another option which I had already been using is to drag the windows title with the mouse and drop it on the Toolbar. You can then open the Resource with a single mouse click (so not really the answer to the question in this thread). (Red Circle 2)

Thanks for the reminder Jonathan and John. I had set up Favorites when I first started using Logs and assigned shortcuts to them, but because I didn't know what my workflow would look like, I never actually used them. Now I've assigned shortcuts to the CSB (English text I'm using now), the NA28 and the BHS.

Fabian

I prefer using the keyboard instead of a mouse when at all possible. Right now I can type "cmd-l" on my Mac to bring up the Library pane. I type "na28" and it's at the top of the list, but since the focus isn't on it, I still have to use my mouse to select it. If the focus was on it, I could just hit return to open it. If I could use an arrow key, or perhaps hit return twice, that would be fine too.

Seems like a small thing, but it's something I do multiple times a day.

Note: I'd even pay a subscription fee for this feature :-)

I requested this before. Command+L works fine until the focus is not on the first entry. So to hit enter will open it.

Same as the Accordance Forums: No one of the developer is listen!

https://community.logos.com/discussion/comment/1309338#Comment_1309338

I requested this before. Command+L works fine until the focus is not on the first entry. So to hit enter will open it.

Same as the Accordance Forums: No one of the developer is listen!

Did you consider the alternatives listed above?

And please remember that Logos is different to Accordance.

Fabian

https://community.logos.com/discussion/comment/1309356#Comment_1309356

I requested this before. Command+L works fine until the focus is not on the first entry. So to hit enter will open it.

Same as the Accordance Forums: No one of the developer is listen!

Did you consider the alternatives listed above?

And please remember that Logos is different to Accordance.

#1 No, because my post relates to the first post from Mark. And it matches a request I have done before. The solution which is given is not the same as requested above.

#2 Not really, both wanna make money. And to features they both think they know it better than the user.

Our goal is simple: If we use the short-cut key to open the library and type right away. The top entry in the search should be on focus, so a simple return opens it. Which is an industry standard. Currently we have then always to use the trackpad or the mouse for clicking on it. Which is not the industry standard.

BTW: Is there a command to type right away in without using a mouse or trackpad. In Accordance you can use the Tab button. Is there a similar for Logos? The Tab only works on certain cases not always.

Thanks

https://community.logos.com/discussion/comment/1309370#Comment_1309370

#1 No, because my post relates to the first post from Mark. And it matches a request I have done before. The solution which is given is not the same as requested above.

#2 Not really, both wanna make money. And to features they both think they know it better than the user.

My comment was about the software and the way one works in one product versus the other.

If you do not accept the solutions offered then make your suggestion at Faithlife Feedback - Desktop - check if there is already one there and vote for it.

https://community.logos.com/discussion/comment/1309014#Comment_1309014

Note that the Command Box can be trained,

The problem with the Command Box is that it's much slower than the Library. My current solution is to make each of my primary Bibles a favorite, and I've assigned a shortcut to each of them. That's working okay, but it's a work-around for something that should be straight-forward.

Right now, if I type Cmd-L to bring up the library, then type "na28" to bring the NA28 to the top of the list, I'm stuck. There's nowhere else to go with the keyboard. I can't hit enter, tab, or up- or down-arrow. Nothing I do with the keyboard makes any difference.

This isn't me trying to make Logos act like Accordance. This is my trying to make Logos work in a way that makes sense.

https://community.logos.com/discussion/comment/1309543#Comment_1309543

Right now, if I type Cmd-L to bring up the library, then type "na28" to bring the NA28 to the top of the list, I'm stuck. There's nowhere else to go with the keyboard. I can't hit enter, tab, or up- or down-arrow. Nothing I do with the keyboard makes any difference.

Curiously this can be made to work on Windows!

Ctrl-L brings up the Library window and, as expected, entering "na28" filters the library.

Then the tab key moves the focus to different panes in the window until getting to the one containing the list of books. You can then use the arrow keys to move up/down the list to get to the required entry. Pressing Enter then opens it.

But I can't see / find an equivalent keyboard function on Mac..

tjebme

https://community.logos.com/discussion/comment/1309543#Comment_1309543

Right now, if I type Cmd-L to bring up the library, then type "na28" to bring the NA28 to the top of the list, I'm stuck. There's nowhere else to go with the keyboard. I can't hit enter, tab, or up- or down-arrow. Nothing I do with the keyboard makes any difference.

This isn't me trying to make Logos act like Accordance. This is my trying to make Logos work in a way that makes sense.

Thanks for highlighting this problem!

Paul

https://community.logos.com/discussion/comment/1309543#Comment_1309543

This is my trying to make Logos work in a way that makes sense.

[Y]

Logos lacks many of the usual Mac navigation options.

https://community.logos.com/discussion/comment/1309750#Comment_1309750

Logos lacks many of the usual Mac navigation options.

Because they want the code to work across multiple devices/platforms they deliberately avoid taking advantage of platform specific features. That keeps our costs down

https://community.logos.com/discussion/comment/1309857#Comment_1309857

Logos lacks many of the usual Mac navigation options.

Because they want the code to work across multiple devices/platforms they deliberately avoid taking advantage of platform specific features. That keeps our costs down

Then why does keyboard navigation work in Windows but not on the Mac?

https://community.logos.com/discussion/comment/1309905#Comment_1309905

Then why does keyboard navigation work in Windows but not on the Mac?

I've never programmed for a Mac so I don't know the answer. But I would suspect that it is influenced by browsers' conventions. I gave up on Mac when the first Mac promised but did not deliver on a true compiler - just interpreters.

https://community.logos.com/discussion/comment/1309912#Comment_1309912

Then why does keyboard navigation work in Windows but not on the Mac?

I've never programmed for a Mac so I don't know the answer. But I would suspect that it is influenced by browsers' conventions. I gave up on Mac when the first Mac promised but did not deliver on a true compiler - just interpreters.

But if navigation works in Windows but not on the Mac, then Logos IS coding for specific platforms. It's not like the APIs aren't available for keyboard navigation on the Mac. I think this reflects a historic bias of Windows over the Mac on the Logos platform (to be fair, Accordance has the opposite bias).

https://community.logos.com/discussion/comment/1309915#Comment_1309915

But if navigation works in Windows but not on the Mac, then Logos IS coding for specific platforms.

This to me is not a logical conclusion. The navigation may work solely because the guidelines used to develop the navigation happen to overlap Windows in this case, iOS in another, Android in yet another ...

https://community.logos.com/discussion/comment/1309919#Comment_1309919

What "guidelines" would those be? Guidelines that were used to create Logos before they ever had a Mac application?

https://community.logos.com/discussion/comment/1309921#Comment_1309921

What "guidelines" would those be?

Whatever guidelines Logos is currently using. The industry is often updating its view of "best practices" and sometimes, a company including Logos, chooses what eventually is shown to be a poor choice. My employer bet on X-boxes on the desktop rather than PC/Mac's [:$]

https://community.logos.com/discussion/comment/1309926#Comment_1309926

Whatever guidelines Logos is currently usin

I'm probably misunderstanding you, but if the guidelines Logos is using are working in Windows but not on the Mac, then that's something that needs to be fixed, because it's broken. Even if the end users have to pay more for it. Even if Logos needs to hand-code their own implementation of keyboard controls.

https://community.logos.com/discussion/comment/1309927#Comment_1309927

I'm probably misunderstanding you, but if the guidelines Logos is using are working in Windows but not on the Mac, then that's something that needs to be fixed, because it's broken.

If Logos says that a particular set of keystrokes results in a particular response, then it is a bug if it does not do so. But it would be surprising if the guidelines used coded to the Mac menu line. There are elements where the OS makes reusable code difficult ... see the current discussion over the L4 form of a link.

John

https://community.logos.com/discussion/comment/1309926#Comment_1309926

Whatever guidelines Logos is currently using. The industry is often updating its view of "best practices" and sometimes, a company including Logos, chooses what eventually is shown to be a poor choice.

After Logos abandoned their old codebase in Libronix, they essentially started over with a clean slate. They made a huge gamble back then on another Microsoft invention called the .NET framework. And a new and not so complete interface called WinForms was the basis for the interface. And yes it was Windows only back then.

Microsoft's true reason for creating the .NET framework was not to provide a superior development platform, but to prevent Java from succeeding in the marketplace. Microsoft had no control over Java which was owned by Sun Microsytems, so they tried to subvert it with .NET

Over the years, Microsoft has seen to it that Windows development is never stable and is constantly changing. Winforms was superceded by Windows presentation foundation (WPF). Which was later superseded with WinUI. Microsoft is currently encouraging developers to move to yet another new thing, WinUI 3.

The gamble Logos made has paid off, because .NET became open-sourced and was embraced (but not without major disagreements) by the Linux community. This gave .NET and its various interpreted languages (C#, Basic, etc) more of a foundation that developers could rely on. It eventually evolved into a cross-platform system, and code written for Windows could run on any other platform that supported the framework. As we know, MacOS is one of those supported platforms.

So Logos as we know it today is a (managed code, non-native) Windows program that just happens to run on MacOS. It is not a native Windows program, nor it is a native MacOS program. It is cross-platform and gives up the performance and control that a native program would have.

This is why I stuck with Libronix over the years. I made a couple of attempts to upgrade but always found the performance lacking. This is also why I ran Bibleworks ... it was native to Windows, written directly to the Win32 API. It was lightening fast (even on old systems) and rock solid reliable.

But now computers and processors have evolved to the point that performance is not so much an issue. Logos runs really good on both platforms. Is it perfect? Of course not. It lacks the power of a native Windows or MacOS program. But it works. And it doesn't crash very often. (I don't run beta's).

This is just my interpretation of things based on what I have seen over the years. If any Logos people see a need, feel free to correct me on anything I said here [:)]

When I started with Accordance 13, it was crashing on me constantly. When I wanted to downgrade back to 12, they told me I couldn't ... they had updated their servers and they no longer supported installing version 12 ... which was the last known stable version at that time. That was my first big clue that something was wrong over there.

https://community.logos.com/discussion/comment/1309939#Comment_1309939

There are elements where the OS makes reusable code difficult

I definitely understand that. And if a Logos engineer tells me that it's not practical for the Mac version to have this sort of parity with Windows, then I'll accept that. Of course if that's true, it supports the notion that programming for Windows is a higher priority than programming for the Mac.

https://community.logos.com/discussion/comment/1309940#Comment_1309940

So Logos as we know it today is a (managed code, non-native) Windows program that just happens to run on MacOS. It is not a native Windows program, nor it is a native MacOS program. It is cross-platform and gives up the performance and control that a native program would have.

Yes, I know. That is the point I was trying to make. It is also the reality that I had to design web applications to 25-years-ago when my team implemented the first administrative systems app over the web at UW. I happen to have hated Libronix ... but then, I still miss Houdini which was state-of-the-art DOS hypertext application from the Nixon era.

https://community.logos.com/discussion/comment/1309942#Comment_1309942

Of course if that's true, it supports the notion that programming for Windows is a higher priority than programming for the Mac.

Or it supports the notion that the Mac conventions are further from the best-practices norm than Windows. [;)]

https://community.logos.com/discussion/comment/1309905#Comment_1309905

Logos lacks many of the usual Mac navigation options.

Because they want the code to work across multiple devices/platforms they deliberately avoid taking advantage of platform specific features. That keeps our costs down

Then why does keyboard navigation work in Windows but not on the Mac?

I don't think it's as clear as that.

Rather there are a few things that work on one platfom that are not implemented on the other - and I don't know why

On the Mac, for example, you can use Shift-Cmd-P to switch between columns and non-columns view in a resource and, as far as I can see, there isn't a similar option available on Windows.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/1309974#Comment_1309974

On the Mac, for example, you can use Shift-Cmd-P to switch between columns and non-columns view in a resource and, as far as I can see, there isn't a similar option available on Windows.

Ctrl+Shift+P

(It appears to be missing from the Help file, though.)

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/1309974#Comment_1309974

Rather there are a few things that work on one platfom that are not implemented on the other - and I don't know why

In the early days of building Logos Desktop, we didn't have thorough specs for all new features, and the Mac and Windows apps were being built by two different teams. Thus, unintentional platform-specific differences crept in. This mostly affects the earliest-implemented (and thus, unfortunately, most core) features, such as Library.

We generally go back and fix up these annoyances when we find them (or when they're reported) but it may take some time to work through them all.

https://community.logos.com/discussion/comment/1310019#Comment_1310019

Rather there are a few things that work on one platfom that are not implemented on the other - and I don't know why

In the early days of building Logos Desktop, we didn't have thorough specs for all new features, and the Mac and Windows apps were being built by two different teams. Thus, unintentional platform-specific differences crept in. This mostly affects the earliest-implemented (and thus, unfortunately, most core) features, such as Library.

We generally go back and fix up these annoyances when we find them (or when they're reported) but it may take some time to work through them all.

Thanks for the explanation Bradley!

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/1309543#Comment_1309543

Right now, if I type Cmd-L to bring up the library, then type "na28" to bring the NA28 to the top of the list, I'm stuck. There's nowhere else to go with the keyboard. I can't hit enter, tab, or up- or down-arrow. Nothing I do with the keyboard makes any difference.

This isn't me trying to make Logos act like Accordance. This is my trying to make Logos work in a way that makes sense.

Thanks for the feature request; I've passed it along.

(BTW, I don't see this as a platform-specific bug. To set the focus to the first resource in the list on Windows, you have to press Tab Tab Tab Tab Tab Tab Down Down Down. If anything, that's a side-effect of some default keyboard focus functionality in Windows common controls, not a deliberate attempt at improving keyboard accessibility that was only implemented on one platform. The keyboard shortcut should IMO simply be Down on both platforms.)

https://community.logos.com/discussion/comment/1310018#Comment_1310018

On the Mac, for example, you can use Shift-Cmd-P to switch between columns and non-columns view in a resource and, as far as I can see, there isn't a similar option available on Windows.

Ctrl+Shift+P

(It appears to be missing from the Help file, though.)

Thanks Bradley!