search

AndBible / and-bible

AndBible: Bible Study
https://andbible.org
GNU General Public License v3.0
588 stars 195 forks source link

Synchronization failure when using css libraries... #530

Open bvahedy opened 4 years ago

bvahedy commented 4 years ago

In build 339: When using jsword/css folder on the local so card for fonts and screen formatting, AndBible fails to sync windows with Hebrew texts. To reproduce: 1) Top window is jps (make sure sync is checked) 2) bottom window hisb (make sure sync is checked) 3) go to Psalms 119:49 4) move the bottom window up by one verse and the top window jumps up 5-6 verses.

Similar issue happens if you tap on a strong's no., upon return from the dictionary, the verse you were on is not where you left off.

You can pick up css library from here: https://1drv.ms/u/s!AgQrBUWnj0-jhT1WqR0OPdGjk3RJ

And HISB bible from here: https://1drv.ms/u/s!AgQrBUWnj0-jgirLC5AGSSlt7t8D

tuomas2 commented 4 years ago

Can't reproduce on my mobile phone.

Duplicate of #488 ?

tuomas2 commented 4 years ago

I will try on my slow 4.4 device (Galaxy S2) later.

tuomas2 commented 4 years ago

Hmmh, could not reproduce it with Galaxy S2 either.

bvahedy commented 4 years ago

Were you able to reproduce #448, if not then it's the same bug. If yes, then it might be a different issue. Let me know if you want me to create a log for this issue. I did create one for #448, but don't know if it was of any help to you.

On Wed, Jan 15, 2020, 8:09 AM Tuomas Airaksinen notifications@github.com wrote:

Hmmh, could not reproduce it with Galaxy S2 either.

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/AndBible/and-bible/issues/530?email_source=notifications&email_token=ALCBRMLSK4O4UNV55LIQ2T3Q54YNNA5CNFSM4KHDHEYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJA3FTQ#issuecomment-574730958, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALCBRMJ3S6AVLFV74DPWEDTQ54YNNANCNFSM4KHDHEYA .

tuomas2 commented 4 years ago

No I haven't been able to reproduce #488 (I assume you mean #488 not #448) any more, after I made my current fix. Before the fix, it was easy to be reproduced. I kind of have idea of why it still happens, but no fix yet. When making the first fix, I the behavior described on this issue as well.

bvahedy commented 4 years ago

Sorry, I meant #488. In the latest build I'm still experiencing same issues of #488 as well as #530.