How to force saving of "interlinear" settings for a particular pairing in multiple books display

"another window" - I should have said "tab"

As to the other questions, I am using the BHW and BHS in "multiple books display" (see screenshot below). The two BHW pairings that I have in this Saved Layout always open with the inline interlinear settings (see red markings in screenshot) the way I had saved them with only the surface text displayed. The BHS + NASB pairing that I'm using, no matter how many times I uncheck the boxes and resave the layout, always opens the way you see it below. Same thing if I open a new tab with BHS + NASB20 (after unchecking the boxes), and same thing if I close and reopen the saved layout. 

I realize that if I switch the order so that the pairing is NASB20 + BHS it will default to having the inline interlinear turned off, but I still have to go through all the clicking because I need the Ketiv Qere turned-on.

Thanks for your help.

I am on Windows 11.
Logos Version info: Logos Bible Study 34.1 (34.1.9)

No that does not match my situation. None of the inline interlinear settings are saved, whether I re-save ("update") the layout or not. If I (1) start from scratch with no tabs open, (2) open the BHS and turn on multiple window display selecting the NASB (or any English version for which I have a reverse interlinear), (3) configure the inline interlinear settings as I need them (I cannot just turn the whole function off, as I have explained above, but the results are the same if I do), (4) save the layout, (5) close all tabs, (6) reopen the layout, the result is that the inline interlinear settings are exactly what they were before I configured them in step (3). They have reverted to default.  

I think this is a new bug. In my old layouts, the settings did save properly. I don't remember having this issue before the most recent couple/few weeks (maybe over a month??). Even now I can open up my old and everything loads and functions as expected, until I open a new tab with resources that were not part of the old layout. As I create new layouts to test the functionality, however, none of the interlinear settings get saved for any resources at all. 

Andrew Batishko said:

There is a two part explanation for this behavior.

First, the inline interlinear settings are not saved as part of the layout. Instead, they are a preference that is loaded every time the resource is opened and saved when the resource is closed. You can see this demonstrated with the following steps.

1. Clear your layout.
2. Open a Bible that supports inline interlinear
3. Turn on the inline interlinear
4. Save the current layout as a new layout
5. Modify the inline interlinear settings (either turn off or turn on a row)
6. Close the Bible
7. Reopen the Bible to confirm that your change still applies
8. Close the Bible
9. Load the previously saved layout
10. Note that the Bible is open with your change applied, not as saved in the layout

Thank you.

So if I understand correctly the values loaded each time for the "inline interlinear" settings are loaded from defaults and not values that are configurable and savable by the user? I observe that the process that you outline above does not change the values loaded for the secondary resource in my use case. It would be sufficient for my purpose if the secondary resource in multiple books display were to load the same settings as the parent resource, but this is not the case. Am I reading this right?

Wolfgang Schneider said:

I followed your steps with  the BHS and the NASB95 in a multiple books display, and have the same problem ... I changed the interlinear setting to have inline with just surface text and manuscriptz, saved this as a layout ... after clsing and reopening the test layout the interlinear setting was changed back to include Lemma, morphology, strongs numbers and louw-nidda info.

Then I added another panel with the NASB95 in it, changed the  interlinear options in that panel to just inline surface and manuscript, saved the layout again, reopened it and the interlinear setting was retained in the separate panel, but not retained in the multiple books display panel

The issue seems to happen when you have the two Bibles (BHS & NASB95) in the same panel and use the multiple books display. If the BHS is the master and the NASB95 the slave in the multiple books display, you have the problem; if the NASB95 is the master and BHS the slave the interlinear setting works as desired.

Thank you for your helpful reply, Wolfgang. I may end up setting things up this way, but it is not my ideal for two reasons:

1. as I mentioned, I need the Ketiv Qere turned-on, so I need to configure that manually every time anyway. 

2. With the English version as the master resource I lose the flexibility to change-out the English translation for the sake of comparison (between Septuagint, Targum, and modern translations, for example).

[quote]

When using multiple resource view, where an inline interlinear setting exists in both the parent and secondary resource, it should use the value stored for the parent resource. The problem with using the value stored for the secondary resource is apparent when the parent and secondary resource both have that setting but with conflicting values (one on and the other off), or where there are multiple secondary resources that provide the same setting that have conflicting values.

Thanks for another detailed reply.  

In this case (primary: BHW - highlighted green, secondary: NASB20 - highlighted orange) there are no shared settings between primary and secondary resources. 

Are you saying the behavior here is explained by the following: (1) Logos tries to load all settings from primary resource (BHW), (2) fails to find most of the settings because they are not attributes of the primary resource, (3) loads default values for the remaining settings?  

I would hope that at step (2) it would look for the settings in the secondary resource, but the current example demonstrates that that does not happen.

I am trying here to rule out the possibility that I might be missing something about how the settings are loaded. If the relevant settings were being loaded from anywhere besides hardcoded defaults, I would have a workaround. If they are hardcoded defaults, clearly I have nothing.