0
Fixed
John Teofilo 1 year ago in Content Creation • updated by Kevin MARHIC (Support Tech) 12 months ago 9

Hi everyone,


I'm currently creating a page with this:

My objective is to create a page with scrollable button below then the sub layout above of it, will scroll to it's target page with anchor. I tried to create a not scrollable button, it works fine on iPhone 5, but not on Android (android phone do nothing if I tap the button).


Any Idea how to do this?


Thank you :)

Answer

Answer

Hello John,


The bugfix for this has been done and will be released within the next version of Android Reader, which will be 4.5.4.6


As a sidenote, there has been a recommendation of one of the devs: if you intend to build your whole magazine with this method (and not just a page with some content), this could lead to problems with memory usage, slowdowns and eventually crashes, so they advise you switch to AVEmag and split your pages across.


Of course if this isn't what you intended to do, you can disregard this.


Best regards,

Kevin

Aquafadas Support

GOOD, I'M SATISFIED
Satisfaction mark by John Teofilo 12 months ago
Under review

Hello John,


Could you send us a .dpe export of your sample project so we can take a look at it? It'll be quicker than rebuilding it.


Best regards,

Kevin

Aquafadas Support

Hi Kevin,


Please the link below for the Test File.

https://drive.google.com/file/d/0B_eaCaHAGZsYaGM5ZHdRa2dLLXM/view?usp=docslist_api


I already test it on iPhone 5, it works fine, but doesn't work on Android devices.


Thank you


Hello John,


Indeed, this seems to be an incorrect behaviour. I am reporting this bug to the dev team for investigation and will keep you updated.


Best regards,

Kevin

Aquafadas Support

Looking forward for Bug Fixed on the next update.


Thank you Kevin

Answer

Hello John,


The bugfix for this has been done and will be released within the next version of Android Reader, which will be 4.5.4.6


As a sidenote, there has been a recommendation of one of the devs: if you intend to build your whole magazine with this method (and not just a page with some content), this could lead to problems with memory usage, slowdowns and eventually crashes, so they advise you switch to AVEmag and split your pages across.


Of course if this isn't what you intended to do, you can disregard this.


Best regards,

Kevin

Aquafadas Support

Hi Kevin,


As the usage concern, I intend to use this method on 1 or 2 pages only,

Thanks for the BugFix :)

Hello John,


This bug has been fixed in the latest version of Android AppFactory and of the standalone Viewer.

Can you check if it solved your problem?


Best regards,

Kevin

Aquafadas Support

Yes it is.. thank you Kevin.