Bug: Notes tab title does not update when renaming Notebook

I am using Logos 8.7.0.0042 on Windows 10 Home.
However I noticed this happening in previous versions of Logos 8.
Workflow resulting in issue
When preparing a sermon I use the following workflow:
1) I duplicate a "template" Notebook on documents.logos.com.
2) In Logos/Notes I search for the duplicated Notebook and then rename it to reflect the text I am working on. In this example the duplicate Notebook is entitled "Sermon prep - template (2)", and I have renamed it to "Sermon prep - Luke 14:7-14".
3) Logos renames the Notebook correctly and opens it.
4) However, the Notes tab title does not rename to match.
5) This means that when you want to create a note from e.g. a Bible, the Notebook name is still the old one, rather than the renamed title.
The good news is that when you exit Logos 8 and restart it, the table title refreshes to the correct one, so it's only a temporary "bug".
Please let me know if you need further information.
Blessings,
Michael
Comments
-
Update: the tab title is also refreshed by simply closing and re-opening the layout. It is not necessary to close the Logos application.
0 -
Michael said:
the tab title is also refreshed by simply closing and re-opening the layout
Even better, just click on All > in the Notes tool, or select another Notebook.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
Even better, just click on All > in the Notes tool, or select another Notebook.
Thanks Dave, that works too.
Either way, it's an extra step which, I suggest, is unnecessary. Better if Logos updates the tab title automatically. [:)]
0 -
Michael said:
4) However, the Notes tab title does not rename to match.
I've just run across this problem again - where renaming the notebook does not update the tab title.
I recognise that all the options mentioned in this thread to update the title do work - but has this been recognised as a bug, will it be fixed?
Thanks, Graham
0