Search Bar
Question: When I desire to open a book from the search bar, and say the book has along title. I select that book. It then opens. However, because the book has a long title the search bear expands to the length of the Title. When it does this the books to the right which I have bookmarks for are hidden and only seen by moving the arrows either left or right. The question is: Is there a way to resize the search bar to its original size? Hope this makes sense.
Comments
-
I assume you are talking about this
That cannot be changed. I am not sure what you mean when you say it is blocking bookmarks. Are you talking about the open Resource tabs?
0 -
Fredc said:
I am not sure what you mean when you say it is blocking bookmarks.
Fred, he's talking about shortcut bar icons (shortcuts). They are simply covered up by the expanded command box.
It is a frustrating problem.
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
As my screen shot illustrates, the icons on my shortcut bar remain visible. Are you experiencing something else
0 -
Fredc said:
When you actually open a resource with a long title (such as CHM Issue 2 in your screenshot), you'll see that the command/search box widens to the right, thus pushing the shortcuts out to the right. I think this has been discussed before.
Have joy in the Lord!
0 -
Thanks for clarifying what I was trying to say. It is frustrating problem, maybe it will be fixed at a later date. Thanks so much
0 -
Fredc said:
As my screen shot illustrates, the icons on my shortcut bar remain visible. Are you experiencing something else
You didn't click on one of those long titles, or you would also be experiencing something else.
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
Example-
Here is my full set of shortcuts.
Here is the shortcut bar with a medium-length title in the command box.
Note that only the first five are visible or usable.
And this is without even talking about how truncated my shortcut bar is over what I'd like, because of the lack of usable space.
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
Hello Doc B
I was having the same issue. At the moment I could only solve it trough a work around.
I enered a very short command in the search box. Go! and the box reduces its size.
Perhaps that helps you until a bugfix comes.
Yours,
Roger
0 -
Doc B said:
Note that only the first five are visible or usable.
And this is without even talking about how truncated my shortcut bar is over what I'd like, because of the lack of usable space.
Is this a Windows issue? I cannot reproduce it on my iMac (OS 10.14.4 Logos 8.5 Beta 1). The Command field clears when I click to open the resource.
0 -
Jack Caviness said:
Is this a Windows issue?
Maybe
Jack Caviness said:The Command field clears when I click to open the resource.
But that's not the issue, the issue is that the command field size is enlarged when the command is typed or when it is selected (and this is unnecessary - the full command is not shown, or possibly is cleared away due to execution faster than we could see the full command in the box) and it stays this way, thus interfering with shortcuts to the right of it.
The bug - maybe only in Windows - is that Logos, when understanding the command we want to be executed, sizes the command box to the length it would need to display that command (even though we won't see it displayed - maybe this used to be the case before L8.5B1) and lets it stay this way. This bug also is behind the workaround to get the field smaller: use a short command string like Close All.
Correct system behavior would be to reset the command field size to a minimum/standard length when it is cleared. Is this what the Mac version does?
Have joy in the Lord!
0 -
NB.Mick said:
But that's not the issue, the issue is that the command field size is enlarged when the command is typed or when it is selected
Should have been more descriptive. When the Command bar is cleared, it is also normal size. Does not appear to be a problem on Mac OS, at least with 8.5 Beta 1.
0