-
[quote user="Reuben Helmuth"]I took the liberty to modify the release notes[/quote] While I appreciate the intent, we generally discourage modifying release notes. Even among Faithlife employees, we try to limit edit rights on release notes to the handful of people who work on or directly with the software development team. That's the drawback of posting
-
[quote user="Mark Barnes"] [quote user="Mark Barnes"]I don't think the Bookstore should be searched by default in an All Resources search. 'All Resources' should be renamed as 'Your Resources' and then the section removed. It belongs in the Everything Search.[/quote] I've changed my mind about this, by the way. I'm finding the section more useful that
-
Summary On February 4, 2020, the operating systems below will enter Maintenance Support status : Windows 7 Windows 8.1 MacOS 10.11 "El Capitan" MacOS 10.12 "Sierra" MacOS 10.13 "High Sierra" By the end of 2020, these operating systems will no longer be supported for Logos Bible Software. Background Microsoft has announced that Windows 7 will be "end
-
[quote user="Jack Caviness"]This error is caused by the resource being an ebook. If search results are to include ebooks, then the link should access the cart on the ebook.logos site.[/quote] This is correct, and I earlier noted it as a known issue on another thread : [quote user="Adam Borries (Faithlife)"] There is a known issue that ebook editions
-
[quote user="DanC"]Is there a way to get my double or triple click to go to a certain book? For example, I have always had Logos go to That's Easy for You to Say with a double click.[/quote] Look up still respects your prioritized resources . I expect what you are seeing is that you are getting a Greek or Hebrew lexicon instead of That's Easy for You
-
The Logos Bible Software desktop application version 8.6 is now available to all users. To immediately update to the current stable version, enter the Update Now command. Otherwise, the app will automatically update the next time it's scheduled to check for updates. Notable New Features Bookstore Search A new section in Basic search, Bookstore searches
-
[quote user="Jack Caviness"] [quote user="Adam Borries (Faithlife)"] This is by design. Pasted text retains source formatting by default, including font face and size. [/quote] Sorry Adam. That is not true. I selected a block of 10pt text from a MS Word document. When pasted into a note, it became 11 pt. [/quote] Sorry, I should have been clearer; I
-
[quote user="Glen Johnson"] I have the same problem. I set 11 as the font size in settings, but when I copy notes from a book to my notes file, the text always shows up in 12. [/quote] (emphasis added) This is by design. Pasted text retains source formatting by default, including font face and size. Pasted plain text should respect your destination
-
[quote user="Mark Barnes"]It would be good to have clarity on where the results come from. All Logos resources? Faithlife eBooks too?[/quote] Yes, as well as resources listed at ebooks.noet.com; there is a known issue that ebook editions do not properly "add to cart" or link to the appropriate storefront. Partially for this reason, Logos editions are
-
[quote user="Reuben Helmuth"] So... apparently certain facets work but other's don't: [/quote] Reuben, it's not the facets that are different; it's the punctuation itself. Or should I say, it’s . The difference is, you are (naturally) typing a straight quote ( ' ), but the Series or Publisher metadata uses a curly quote ( ’ ). The Find resources
-
Kiyah, done.
-
[quote user="Kiyah"] But with Faithlife it seems to be all or nothing when it comes to Verbum.[/quote] Kiyah, I appreciate your desire to take holistic view of Church tradition. However, Verbum is an intentionally distinct brand with a different audience than Logos. Even the "Set Verbum to Yes" command is somewhat outdated (and subject to deprecation
-
[quote user="Hans van den Herik"]The Text in the Workflow editor [response fields] is red underlined and seen as incorrect. The same text as a separate note (in the note application) isn't underlined. The spelling is there seen as correct. [/quote] Hans, I'm sorry for the inconvenience. The issue here stems from the fact that the workflow response fields
-
Hi, Reuben, Thanks for your thoughts. Workflows and Notes development are on hold for now while we work on other features. We'll keep fixing bugs as needed, but no new improvements are planned in the immediate future. We are intentionally limiting the scope of new feature work to just a few things at a time. Right now, that includes the Selection Menu
-
[quote user="Adam Borries (Faithlife)"] the search button: always searches inline on short selections (1-5 words). on long selections in non-bibles, opens a search panel for "All Resources." on long selections in Bibles, is omitted on the Selection Menu to make room for other actions. ... Having said that, it might not be a bad idea to have the Search
-
1. There are many phrasal nouns which can be looked up directly as a headword. e.g., "love of God," "kingdom of God," "holy people," "Holy Spirit," "Sea of Galilee," etc. 2. There are other phrases that have an LCV equivalent or alias, like those you mention. "Jesus Christ" etc. Parsing phrases for Look up via the Context Menu would be new work that
-
Currently, the Study command performs the first available action in this order: Open Factbook when any Bible Knowledge entity (Person, Place, Thing) is present Open Bible Word Study (for a single word) in Bible text. (This respects the "Prefer Lemmas" setting when applicable; but there is a known issue that the lemma is passed with incorrect characters
-
[quote user="Graham Criddle"] I was surprised to see the search option from the new selection menu running an Inline search as opposed to opening a search panel. [/quote] Just as a point of clarification, the search button: always searches inline on short selections (1-5 words). on long selections in non-bibles, opens a search panel for "All Resources
-
Thanks, Mark, that's good feedback.
-
[quote user="Reuben Helmuth"]Recently the behavior was changed to automatically anchor the note to the current reference when hitting the New Note button. [/quote] Yes, the New Note button now defaults to anchoring the note to the active reference or selected text range. This was introduced in 8.5 beta 1, and shipped to stable today. Much of the value