BUG: Remaining bug with 'in-resource' favorites panel
In the Favorites panel within each resource, there is an area where the on-screen text (see below) advises that you can save a favorite article, passage, person, place, thing, or document.
However, the only items that will remain in this section are favorites (bookmarks). There is no way to save a person, place, thing, or document in this area. Anything dragged and dropped here disappears when you close the resource and open it again, except for favorites (bookmarks) connected to the resource itself.
Previously, there was an issue where the "Add" button would not appear until you closed and reopened the Favorites panel. Additionally, the favorites you did save would not show unless you added one using the "Add" button. These issues seem to have been resolved in the latest Beta 39 update.
The remaining bug prevents anything else from being permanently saved in the panel. This is a consistent issue. I can save documents, notes, and favorites from other resources, which appear and remain in the main Favorites panel when I save them, even though they mysteriously disappear from the "in-resource" panel.
Logos assistance would be appreciated.
👁️ 👁️
Comments
-
did this get addressed?
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
There is no way to save a person, place, thing, or document in this area. Anything dragged and dropped here disappears when you close the resource and open it again, except for favorites (bookmarks) connected to the resource itself.
This functionality is by design, and is not a bug. The Favorites sidebar within the book panel is intended to only display favorites that are directly connected to the book itself. The solution to the confusion of having the new favorites vanish on reopen might be to prevent them from being added via the book sidebar in the first place.
However, the instructions that you mentioned are confusing in the context of the resource panel, and I've created a case to alter that text to more accurately explain the usage.
Andrew Batishko | Logos software developer
0 -
