BUGS: V36 ... visual filters and sidebars
Okay, I have officially had it:
- As sometimes happens, a new release results in random turning on of visual filters. This time it was in my preferred Bible with filters I haven't used for months. 4 filters had to be turned off.
- EVERY time I open my preferred Bible the right panel/sidebar reappears. I immediately turn it off ... and it stays off as long as I don't close and reopen the Bible.
This is always an annoying distraction as both are items that supposedly remember state.
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."
Comments
-
Bumping in hopes of getting an appropriate answer
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 -
MJ. Smith said:
This is always an annoying distraction as both are items that supposedly remember state.
Both of these issues are certainly annoying and need to be resolved
👁️ 👁️
0 -
MJ. Smith said:
EVERY time I open my preferred Bible the right panel/sidebar reappears. I immediately turn it off ... and it stays off as long as I don't close and reopen the Bible.
This shouldn't be happening, and I've been unable to replicate it.
The behavior is supposed to be that while the right sidebar is on by default in Bibles, each Bible will save your preference.
That behavior had to be reset in v36, so if you close the sidebar in v35 it might reopen in v36. But after that, it should remember your preference for that Bible version.
The preference is also saved in layouts, so if you open a Bible from a layout, the sidebar will be open/closed depending on how that layout was saved.
Users have asked for a way to turn it off/on across all Bibles. That's not currently possible, but it's something we're considering. But first, I want to be confident that our existing implementation isn't buggy.
0
