Steve,
I gave you information on how the application is designed. I know the code I wrote, and I know how it is supposed to behave. I did not disregard what you told me or ignore the symptoms you reported. I just mentioned how it's supposed to work, and how it works on all of my devices (12+ Android tablets). I should mention that MobileSheets only loads a certain number of pages forward and backward (5 forward and 3 backward, so including the current page, that's 9 pages). I can load a 5+ page song and turn through every page without a single delay if the PDF is well optimized. I can also load a very, very slow document, and if I turn through pages quickly, most will still be rendering in the background, but once they've all loaded, I can turn back and forth with no delay at all, but only up to the amount that is cached. The limitation here is in terms of the amount of memory the operating system will allocate. Some devices will give MobileSheets far less memory to work with, but even with devices with a lot of memory, the OS may limit the amount MobileSheets is allocated to 512-1024 MB. Just to be clear - I can't just request whatever amount of memory I want. The OS lets apps ask for a "large" memory allocation, but there is no guarantee that the OS will honor that, or what that amount will be. So having any sort of setting for this in MobileSheets doesn't really make any sense as MobileSheets doesn't have much control over it. I should mention that if MobileSheets tries to render too many pages and an out of memory exception is thrown, then MobileSheets will cut the number of pages cached in half. This can even happen multiple times until MobileSheets is only rendering the current page. If your device is having major issues, this may be the case for you. My Google Pixel Slate (also a chromebook) displays two pages at once just fine. What type of Chromebook are you using?
Also, if you want me to test your file, you can email it to mike@zubersoft.com and I'll be happy to try it out.
Mike
I gave you information on how the application is designed. I know the code I wrote, and I know how it is supposed to behave. I did not disregard what you told me or ignore the symptoms you reported. I just mentioned how it's supposed to work, and how it works on all of my devices (12+ Android tablets). I should mention that MobileSheets only loads a certain number of pages forward and backward (5 forward and 3 backward, so including the current page, that's 9 pages). I can load a 5+ page song and turn through every page without a single delay if the PDF is well optimized. I can also load a very, very slow document, and if I turn through pages quickly, most will still be rendering in the background, but once they've all loaded, I can turn back and forth with no delay at all, but only up to the amount that is cached. The limitation here is in terms of the amount of memory the operating system will allocate. Some devices will give MobileSheets far less memory to work with, but even with devices with a lot of memory, the OS may limit the amount MobileSheets is allocated to 512-1024 MB. Just to be clear - I can't just request whatever amount of memory I want. The OS lets apps ask for a "large" memory allocation, but there is no guarantee that the OS will honor that, or what that amount will be. So having any sort of setting for this in MobileSheets doesn't really make any sense as MobileSheets doesn't have much control over it. I should mention that if MobileSheets tries to render too many pages and an out of memory exception is thrown, then MobileSheets will cut the number of pages cached in half. This can even happen multiple times until MobileSheets is only rendering the current page. If your device is having major issues, this may be the case for you. My Google Pixel Slate (also a chromebook) displays two pages at once just fine. What type of Chromebook are you using?
Also, if you want me to test your file, you can email it to mike@zubersoft.com and I'll be happy to try it out.
Mike
