Crash While Preparing Passage Guide

Dale Durnell, Retired UM Clergy

Opened L4 and opened Passage Guide

Opened UM Lectionary, scrolled to next week's readings and clicked on Epistle lesson.

Copied the first of two reading from James, moved cursor to selection box in PG and pasted the text.

Started PG

Clicked on "Add" while PG was building and program crashed.

Log file is attached

Dale

 P.S. Here's another concern about the PG. I rarely want all the "stuff" that comes up with a PG. I don't care about verb rivers, "interesting words" and the myriad other things that show up on the list. Primarily, I use the PG as a quick way to access my commentaries, but the majority of "stuff" that keeps coming up is of no interest to me. I've "turned it off" but when I start a new PG, it comes right back.

I'd really like it to stay turned off, and if I decide I want more, I want to be able to click "add" to put that material back in and then I can click "refresh" and get the new material. For me that's preferable to having to shut off a dozen features I don't want every time I run a PG (which is always weekly and occasionally two or three times weekly as I build my sermons in advance)

But, that's just how I do business -- obviously others might want to do thing differently

Dale Durnell, Retired UM Clergy

restarted L4 after the crash, clicked on PG to start over, found it automatically restarted the PG I was working on, and the program crashed again. I've attached the latest file from that crash, but I don't know if you're going to get both log files or just the latest twice

Dale

Dale Durnell, Retired UM Clergy

PG keeps crashing now -- been using it quite a bit the last few days, but after the crash today, any return to the passage being worked when the program crashed causes it to crash again. If I can quickly insert another passage (e.g., Gen 1) the PG continues without a hitch. But, if I then reinsert the desired passage (the one from James) the program immediately crashes.

Dale

Here's the latest log

George Allakhverdyan

https://community.logos.com/discussion/comment/10111#Comment_10111

Hi thanks for the logs. It seems this issue has been previously logged and should be fixed in Beta 2.