Sync to Farthest Location

I would like to suggest Logos add a comment to go to farthest location similar to the Kindle. I often read a book on my desktop during the day and want to continue reading at night from my iPad, but when I open my iPad I am at the same location I ended at the evening before.

Find more posts tagged with

Mobile App

Comments

JT (alabama24)

Ugh. I'm tired of talking about this subject... (It's not your fault Keith, its Logos).

I would like to suggest Logos add a comment to go to farthest location similar to the Kindle.

Logos already does have this feature, but it needs some adjustments. The problem is actually in what Logos means by "layouts," and how they have implemented them.

In L4/L5, when you have a book open in what Logos calls a "layout," the location data is saved. The book will always open back up to where you left off. Here's my beef. Logos has misnamed "layouts." They shouldn't be called that at all. They should be called something like "projects." When you save a layout project, the guides that you were using and resources that were open stay put. And they should be. When you are doing sermon prep three weeks in advanced, you will want to have your layout project keep everything in place. By doing so, you can pick up and drop your work at anytime without losing your place.

The term "layout" should be reserved for the pattern of tiles on the screen. Projects should be independent of those layouts. I have two computers, an iPhone and an iPad. I would NEVER want the same layout on any of those devices. My desktop monitor is 2.5 times the size of my laptop screen. The same pattern and size of tiles doesn't make sense on my desktop... nor does it make sense on my iPad. Nevertheless, I DO want to access my PROJECTS on those various devices. I want to pick up where I left off, seamlessly. The layouts will be different, but not the content.

Here is the deal with the iOS mobile apps. Logos has implemented them as if they were a saved layout (by their definition). When you have a resource open, it stays put. Logos already does sync location data... but it isn't intuitive nor easy to use. Logos needs to implement some form of "projects," and enable them on mobile. In that way, the user can seamlessly move back and forth with location data... and not just to the "furthest location," and not just to a single location.

FWIW - If you want to utilize the sync location as it is currently implemented, follow these steps:

Make sure the resource IS NOT left open in EITHER panel on the mobile app when you close it.
Open L5 to a BLANK layout.
Open the resource from the library. As long as you allowed the mobile app to sync, it should open to where you left off on mobile.
Allow L5 to sync and close the resource.
Open the mobile app and then open the resource. It should open to where you left off within L5 (as long as you allowed it to sync, and as long as you didn't open a layout with the resource open).

toughski

https://community.logos.com/discussion/comment/562630#Comment_562630

good ideas, Alabama!

Keith Larson

https://community.logos.com/discussion/comment/562630#Comment_562630

FWIW - If you want to utilize the sync location as it is currently implemented, follow these steps:

Make sure the resource IS NOT left open in EITHER panel on the mobile app when you close it.

Open L5 to a BLANK layout.

Open the resource from the library. As long as you allowed the mobile app to sync, it should open to where you left off on mobile.

Allow L5 to sync and close the resource.

Open the mobile app and then open the resource. It should open to where you left off within L5 (as long as you allowed it to sync, and as long as you didn't open a layout with the resource open).

I was hoping for something easier!

BTW how do you close a resource (step 1)?

Graham Criddle

https://community.logos.com/discussion/comment/562728#Comment_562728

BTW how do you close a resource (step 1)?

You open another resource "over it"[:)]

Keith Larson

https://community.logos.com/discussion/comment/562729#Comment_562729

BTW how do you close a resource (step 1)?

You open another resource "over it"

The original post made it sound like you had to totally close ALL resources. I already knew about opening a new resource over a previous one.