4.2 Beta 1: Paged View bug

Rosie Perera · 2010-10-07T16:11:07+00:00

* Open Logos with a blank layout, maximized. * Open a book and jump to somewhere in the middle of it (the one I opened was already open somewhere in the middle of the book; the main point is don't just open it to the Title page; it's got to be somewhere where columns will work). * Turn on Paged View * Tools > Highlighting…

Rosie Perera

Open Logos with a blank layout, maximized.
Open a book and jump to somewhere in the middle of it (the one I opened was already open somewhere in the middle of the book; the main point is don't just open it to the Title page; it's got to be somewhere where columns will work).
Turn on Paged View
Tools > Highlighting
Drag the right edge of the book window all the way over to fill the remaining blank space in the layout (it should now display in two columns)
Click in the book window somewhere to bring the focus there (not sure why it doesn't go back there from the Highlighting window when you drag the size of the window, but it doesn't; but that's a different issue).
Page Down once or twice
Page Up a few times (several times more than you paged up) until...

Suddenly, after a longer pause than the previous few Page Ups, Page View redisplays in single column mode. Paging down from there will not make it go back to two columns. Verify on the panel menu that it's still in Paged view.

The book this happened in for me was The New Testament and the People of God (N.T. Wright). I initially opened it to about chapter 3, section 3, and it went back into single column mode once I'd paged back up to about chapter 3, section 2. I'm using a 13" monitor.

Here's my log file: 0284.PageViewBug.zip

Find more posts tagged with

Comments

steve clark

<deleted, timed out for full delete>

Rosie Perera

https://community.logos.com/discussion/comment/179964#Comment_179964

Hey Rosie,

isn't paged view in 4.2 beta ?

Oops, yes. Good catch. Thanks! Fixed. You can delete your post now if it's not too late.

Jacob Carpenter (Faithlife)

https://community.logos.com/discussion/comment/179966#Comment_179966

Rosie--

This sounds kind of like the behavior mentioned under the known issues in the release notes:

Content that is too wide for the optimal column width can force fewer columns. Scrolling past the wide content never restores optimal width columns. Toggling paged view or resizing the window will restore optimal width columns.

I'll look into it tomorrow, but my guess is that there is some content in an article that's being loaded that is too wide for the two column display. It's also possible, since you're going up, that you just haven't gone far enough to see what it is (likely a table or a heading).

Rosie Perera

https://community.logos.com/discussion/comment/180071#Comment_180071

Rosie--

This sounds kind of like the behavior mentioned under the known issues in the release notes:

Content that is too wide for the optimal column width can force fewer columns. Scrolling past the wide content never restores optimal width columns. Toggling paged view or resizing the window will restore optimal width columns.

I'll look into it tomorrow, but my guess is that there is some content in an article that's being loaded that is too wide for the two column display. It's also possible, since you're going up, that you just haven't gone far enough to see what it is (likely a table or a heading).

OK, that must be it. There was some text a couple of pages back that must have been a table (p. 59):