CRASH: Read Aloud crashed when topic filter enabled in ESV

Page 1 of 1 (6 items)
This post has 5 Replies | 2 Followers

Posts 1367
JimTowler | Forum Activity | Posted: Wed, Oct 29 2014 7:26 AM

I "discovered" that the Factbook topic offered to open all 111 references for "Forgiveness". I had no idea how or that it could do such a thing, so clicked, and it opened ESV with a filter mode enabled. Anyway - to push my luck - I started Read Aloud.

Well, at the end of the first section, instead of either A) skipping to the next filter section and reading on, or B) reading with disregard to the filter, it choose C) CRASH!!!

Ops!

Posts 244
LogosEmployee
Ryan Gano (Faithlife) | Forum Activity | Replied: Wed, Oct 29 2014 8:10 AM

The crash in read aloud is a known issue (we're actively working on a solution). It's actually unrelated to the filter. In the case you've outlined it should choose B and keep reading.

We plan to have a fix for this very soon.

Ryan

Posts 1367
JimTowler | Forum Activity | Replied: Wed, Oct 29 2014 8:30 AM

Thanks Ryan.

(A) would be best in that context, honoring the filter, but (B) is way better than (C). I'll await the fix ...

Posts 244
LogosEmployee
Ryan Gano (Faithlife) | Forum Activity | Replied: Wed, Oct 29 2014 1:26 PM

Ryan Gano:
We plan to have a fix for this very soon.

We have published a new resource. When you get that update the ESV should read correctly as you progress through chapters. We also have a code fix in place to make the app more resilient in the future. (The code change is not in SR1)

Posts 1367
JimTowler | Forum Activity | Replied: Thu, Oct 30 2014 1:56 AM

Hi Ryan,

Just to confirm: SR1 and the ESV update or whatever fixed the crash during Read Aloud.

And yes, it carried on reading past the filtered text and the ball kept bouncing on the 1st line of the next filtered section. Not really right, but not totally broken. At least not a crash. Better would be to respect the filter boundaries, but that's a whole new level of complex that I expect is not important, or at least low priority.

Thanks Faithlife on the fast turnaround as these bugs are coming to light now its out of the limited Beta test cycle.

Posts 244
LogosEmployee
Ryan Gano (Faithlife) | Forum Activity | Replied: Thu, Oct 30 2014 7:00 AM

JimTowler:
Not really right, but not totally broken. At least not a crash. Better would be to respect the filter boundaries,

I agree. I wish we were able to implement the behavior you describe. Unfortunately the read aloud code would have required quite a bit of work to support it. Maybe someday. Big Smile

Page 1 of 1 (6 items) | RSS