BUG: Cannot change to a specific page in many books

This applies to both Logos and Vyrso on the iPad.

In some books I cannot change to a specific page in any way. I cannot enter a reference. I cannot use the scroll bar.

For example, Luther's Works, vol. 27, I can use the ToC to jump to the beginning of a section. I can also use the scroll bar, but only to jump to the beginning of a section. If I try to enter a page reference in the reference bar, nothing happens. If I try to use the scroll bar to move to the middle of a section, I just get taken back to the beginning of a section. Aside from paging through one page at a time, I cannot navigate to a specific page.

Very frustrating.

Find more posts tagged with

Comments

Sort by:
1 - 2 of 21

    Hi Martin

    I don't have the resource 'Luther's Works' so cannot test it. Does the resource actually have page numbers? Some resources were produced without them. If you see page numbers at the bottom of the screen then you should be able to type 'Page xx' in the search bar and have it work.

     

    tootle pip

    Mike

    Now tagging post-apocalyptic fiction as current affairs. Latest Logos, MacOS, iOS and iPadOS

    Hi Martin 

    The function you are witnessing as missing is "resource associations"--Something we had in Libronix, have in Logos 4, but has not moved to mobile. At this time you will have to open the individual volume you want to read, or search through. Using the reference box will not take you from one volume in the series to another. I don't know if or when it will be implemented. 

     

    Hi Martin 

    The function you are witnessing as missing is "resource associations"--Something we had in Libronix, have in Logos 4, but has not moved to mobile. At this time you will have to open the individual volume you want to read, or search through. Using the reference box will not take you from one volume in the series to another. I don't know if or when it will be implemented. 

    Tommy, I don't think this has to do with resource associations.  It sounds like Martin just wants to enter a page number in the current open volume and go to it.  I can enter "234" in the reference box in Logos 4 Windows, and it jumps to page 234.  Can the same thing be done in iOS? (I don't have an iOS device)

    And, FWIW, the Luther resources do have page numbers. (By the way, L4Win does not accept a page number entry when I am on the title page of any of the Luther's Works volumes.  The title pages don't have a page number.  If I scroll down to a page that is numbered, then I can enter a new page number in the reference box.  In other books that have page numbers, the title page is also numbered.  So the Luther resources are peculiar in this respect.)

    MacBook Pro (2019), ThinkPad E540

    My bad. For some reason I though Todd was attempting to cross volumes. I do think I know what the problem is. In the iOS version of Luther's works the page numbers at the bottom read.

     

    Vol.#.Page#-Vol.#-Page#. (i.e. for Luther's works Volume 1 page 234 "1.234".

    Martin, if you'll notice after swiping to changes pages, and seeing what is already in the reference box when having it appear you'll see VpX.XXX. Changing the number there in any way does nothing. I'm looking into whether that is a bug or not. 

    In contrast, using page numbers in the reference box in the WBC series for instance does work. 


     

    Yes, I noticed the difference in page numbers. And believe it or not, I actually AM able to tap references to other volumes of Luther's works, and they do open, and to the referenced page.

    I'm guessing it is a bug due to the manner in which page numbers are specified in this particular resource.

    Yes, I noticed the difference in page numbers. And believe it or not, I actually AM able to tap references to other volumes of Luther's works, and they do open, and to the referenced page.

    I'm guessing it is a bug due to the manner in which page numbers are specified in this particular resource.

    Is volume 1 the only one in Luther's Works that you've noticed has this issue?