To set two columns invariably

Hi, I am using iPad Air 2 with Vyrso.

I would like to know why I set that I want to read in two columns (portrait mode), but the application insists on some pages show only one column, as if in automatic mode. In short, it is as if the two columns were the same as the automatic, because the text will change to one column, especially if there is any figure or table. The interesting thing is that even on pages where there are figures or tables, sometimes it shows in two columns, sometimes shows in one.

Sorry my bad English.

I live in Brazil.

Thanks.

Find more posts tagged with

Mobile App

Comments

Mike Binks

Hi Agnon

I seem to remember that this is a long standing oddity.

It is logical that the app should change to single column when it meets diagrams and pictures that would be unreadable in two column mode. However it also does this when it meets captions and some other text that is not set to line break.

Once it has moved to single column it does not or didn't used to revert to single column.

This, as I say, is my memory of the situation. I don't use multi-column settings myself as I prefer to scroll quickly rather than turn pages.

JT (alabama24)

I would like to know why I set that I want to read in two columns (portrait mode), but the application insists on some pages show only one column, as if in automatic mode.

Mike pretty much has the right answer. There are some elements in resources which are "fixed width." These include tables, pictures and (sometimes) headings. Once the app encounters a fixed width element which is wider than the column, it switches to single column and isn't smart enough to move back later.

The interesting thing is that even on pages where there are figures or tables, sometimes it shows in two columns, sometimes shows in one.

This is explained by having elements which are narrower than the column width.

Agnon Fabiano

https://community.logos.com/discussion/comment/863780#Comment_863780

Thank you! But I want to show a exemple. To see that it sometimes to adjust the image (Mapa 2), it sometimes not adjust.

JT (alabama24)

https://community.logos.com/discussion/comment/863799#Comment_863799

If this is the resource in question, and if there is nothing nearby that could have caused the switch, I am stumped.

Alan Palmer (Logos)

https://community.logos.com/discussion/comment/863799#Comment_863799

I was able to reproduce your behavior and I hope that I can offer an explanation:

In this case the content that is causing the column fallback to 1 is not the image. It resizes appropriately, as you demonstrated. It is in fact some tables in the article preceding this one.

When jumping directly to the article (avoiding the previous article from being included in the "loaded area") this content fits 2 columns. However, our column fallback feature takes into account all loaded content so when the preceding article is still loaded (as is the case when scrolling down to this content from above), it uses only one column.

I hope that helps at least to offer some rationale behind this strange behavior.

Agnon Fabiano

https://community.logos.com/discussion/comment/864050#Comment_864050

Thank you!