Beta 6: Nice column options---can one column be added as an option?

Todd Phillips · February 2011

Since the "auto" option still doubles the columns at narrower widths than I prefer, can "1 column" please be added as an option?

Fred Chapman · February 2011

Todd Phillips said:

Since the "auto" option still doubles the columns at narrower widths than I prefer, can "1 column" please be added as an option?

Todd you are probably already aware of this, but if you select none it reverts to 1 column, however it does return you to paging through with the scroll bar instead of the page view arrows.

Todd Phillips · February 2011

https://community.logos.com/discussion/comment/217689#Comment_217689

Fred Chapman said:

Todd Phillips said:

Since the "auto" option still doubles the columns at narrower widths than I prefer, can "1 column" please be added as an option?

Todd you are probably already aware of this, but if you select none it reverts to 1 column, however it does return you to paging through with the scroll bar instead of the page view arrows.

Yes, But sometimes I find it nicer to read in paged view (with the extra margins), and I don't want it to split the columns.

And since they're already got 2,3,4 and 5, why not add "1"?

P.S. I'd prefer a column width control, but this is better than nothing.

Rosie Perera · February 2011

https://community.logos.com/discussion/comment/217691#Comment_217691

Oops, I hadn't seen this thread when I posted my query/bug/request - http://community.logos.com/forums/t/29431.aspx.

What I suggested would be mutually exclusive with what you're requesting, so we might have to duke it out. I didn't think the word "None" was intuitive for turning off paged view because it gets you back to one column, not zero. If they add a "1" column view in paged view, as you're requesting, then perhaps it would be more obvious that "None" is for turning off the columnar view. But there's still always one column in scrolling view, so "None" still isn't the best word for it. Any other suggestions? Normal?

Dave Hooton · February 2011

https://community.logos.com/discussion/comment/217871#Comment_217871

Rosie Perera said:
. Any other suggestions? Normal?

I suggested Off in your thread (having seen the others).

Melissa Snyder · February 2011

Todd Phillips said:

Since the "auto" option still doubles the columns at narrower widths than I prefer, can "1 column" please be added as an option?

I've submitted a request to consider adding a one-column option for paged view.

Jerry M · February 2011

https://community.logos.com/discussion/comment/217930#Comment_217930

On my monitors as long as your slider on the font size for a resource is at least one line above normal and the resource only takes up one half of the monitor or less, then when you put the column selection on auto, it makes one very nice column with larger margins. Is this everyone else's experience?

(edit: On some resources you have to move the font size slider two lines bigger or move the window size one size smaller than one half the display.)

Jerry M · February 2011

https://community.logos.com/discussion/comment/217959#Comment_217959

This is also dependent on program scaling and default text size in the program settings. Actually it appears that it is programmed so that if the resource takes up one half or less of the screen and the font slider is set on average and the program settings are on 100%, then you get one column in the auto setting for columns. Of course the requested change would definitely be welcomed.

Adam Olean · February 2011

Auto generally works for me, but I definitely appreciate these new options. The only problem that I see is that highlighting in the margins squeezes the column width (e.g., the "Left Margin Bar Red" highlighter under Emphasis Markup). This messes up the automatic-columns setting. I wonder if this could be corrected. The margins could be made to compensate for this; or, perhaps, marginal highlights could be tweaked to function differently. I avoid highlighting in the margins because of this issue.

Rosie Perera · February 2011

https://community.logos.com/discussion/comment/218400#Comment_218400

Adam Olean said:
The only problem that I see is that highlighting in the margins squeezes the column width (e.g., the "Left Margin Bar Red" highlighter under Emphasis Markup). This messes up the automatic-columns setting. I wonder if this could be corrected. The margins could be made to compensate for this; or, perhaps, marginal highlights could be tweaked to function differently. I avoid highlighting in the margins because of this issue.

Could you show us a screenshot of what you mean by "messes up the automatic-columns setting"? I can't see any messed up or unexpected behavior when I play around with bars in the margins and auto column settings, resizing the window width, etc.

Adam Olean · February 2011

https://community.logos.com/discussion/comment/218466#Comment_218466

The text and the highlights share the same preset margins, so marginal highlights expand the white space and squeeze the text. The automatic columns do not correct for this; so with highlights, the text becomes becomes skinnier when the columns are at either their widest or narrowest on the automatic setting (cf. screenshots 1-4). They get quite narrow before reducing to fewer columns (screenshot 4). I think it would be preferable if it reduced to fewer columns sooner when marginal highlights are present, but perhaps that would not be easy to accomplish. Good thing, we have some manual settings.

I did find one one odd behavior. If I scroll beyond Genesis 1 (which contains my highlights) the text continues to be "squeezed," from the marginal highlights. But if I jump from Genesis 1 to later chapters or books of the Bible (about 10+ chapters), then the text will completely fill the margins again. Finally, if jump back to a chapter near Genesis 1 (e.g., Gen 5) and then page up to it Genesis 1, the highlights do not fit into the preset margins---they overlap. See the effect in the last screenshot.

To summarize. Jump to Genesis 1 and then it loads as expected (screenshot 5). Jump near Genesis 1 and it does not load as expected (screenshot 6). Might this have to do with how Logos preloads text?

Anonymous · February 2011

https://community.logos.com/discussion/comment/218570#Comment_218570

I suggest the word Scroll or Scrolled instead of None.

Clinton Thomas · February 2011

Beta 7 has "1" as one of the options. Added a one-column option for paged view to the resource panel menu. (http://community.logos.com/forums/t/29407.aspx)

Nice