-
Hi Mickey, The next release of Logos (9.3) which will be a few weeks will automatically disable the hardware acceleration which is causing the issue. It is available now in beta which if you can find more about how to join by looking at the stickied threads at the top of the beta forum If you do not want the risk of using a beta, you can manually apply
-
[quote user="MJ. Smith"] In the Bible Browser, each restriction is considered independently. [/quote] Thanks for this, I was not aware. Quite strange considering how the other tools with facet filtering work, as may lead to wrong data.
-
Having said that it might be that it is both allusion and quotation....
-
The BB is showing Pro 10:13 as being a quoted in 1 Cor, however it is only an allusion. That verse is however quoted in 1 Peter. Perhaps there is a slight error in how the BB is collating the data.
-
https://feedback.faithlife.com/boards/logos-desktop-app/posts/add-support-for-tables-in-notes is something you can vote on or contribute to.
-
With a change in Program Scaling, the default 3 ticks from left does not change, however with Content Scaling changes, the default position will change, going further to the right as the Content Scaling increases, and vice versa. If the resource is set on the default position, and you change the content size, the bar will move and still be on the new
-
Hi Mike, welcome to the forum. I the Program Settings you can also change 'Content Scaling' as a percentage. This will allow you to set the default size to something suitable. You can find it under Tools -> Program Settings -> Accessibility -> Content Scaling. If you use this along with 'Program Scaling' you should be able to get the sizes
-
Yes they do, I should of posted that last image first it would of made things clearer for you and Dave. Thanks for looking anyway folks 👍
-
Great news thanks Kyle
-
There is a difference between the two popups Also problem seems to be for every milestone in the book, 3:7 was just an example.
-
The problem Mike is that a Commentary section in a guide linked to a bible does not show this commentary unless it is on the start of a range.
-
Yes there was Charles, and is as you describe. If you wish to view it the old way, from that plan page, click the icon in the top right and choose 'Open Resource' and that should have the traditional reading plan markers in your bible.
-
IVP New Testament Commentary (Revelation) I am trying to follow and have noticed some milestone issues. It looks like only the first part of the milestone in the commentary is actually linked, not the range. Eg The Message to Philadelphia (3:7–13) If I am in my bible on 3:7, then in the commentary will show in a linked Commentary Guide. If I am
-
Would it not be easier if Verbum packages and resources were just Logos packages and resources, and the Verbum specific features were just made available in Logos for all if they wish to use them? Then everyone would be on the same page no matter which denomination they are.
-
Looks like they have pulled the expansion for now - it is no longer showing, maybe they are removing it.
-
Thanks folks - I was aware of this older one so good to know
-
There are three International Standard Bible Encyclopedia in the Factbook Expansion . I know about these two.... The International Standard Bible Encyclopedia (ISBE), 1915 Edition International Standard Bible Encyclopedia | ISBE, 1979–1995 (4 vols.) However there is a third just titled ... International Standard Bible Encyclopedia for $79.99.
-
[quote user="Stephen McCracken"] It was looking at Factbook Expansion that I saw its Logos price. Now that I have gone back to the website (a few hours later), the Logos Expansion dynamic price has reduced about £150 from the earlier dynamic price!! So it is a better deal through a packages as you point out. Thanks [/quote] I thought it had changed
-
Not quite what I meant but glad it working now
-
[quote user="Graham Criddle"] We added in a new plugin - can't think of anything else we have changed recently [/quote] Sorry I meant did you toggle this setting in the reftagger plugin....if so it may just be stale cache, but if it always been like this then probably just the plugin not working properly. Jan's solution sounds good. I am too unfamiliar