A14 crashes when using Gesenius' Grammar

Gesenius' Grammar opens to the Title Page (although all it shows is a note about the first edition).

When I attempt to go to any other page, either by scrolling, by clicking on a section in the contents pane, or by typing in a paragraph number in the navigation window, L4 immediately shuts down.

I've attached my log. Thanks for your help. Greg

3465.Archive.zip

Find more posts tagged with

Comments

Tom Philpot (Faithlife)

Greg,

I made some changes to scrolling for A15 and I've tried to reproduce the crash you're seeing but wasn't able to. Can you update this thread once A15 is out if you're still seeing this crash?

Tom Philpot (Faithlife)

https://community.logos.com/discussion/comment/101523#Comment_101523

Greg, could you post a screen shot of the resource when it's loaded. You can use Cmd+Shift+4 to grab the screenshot and it will save to your desktop.

One other question: Are you using Logos 4 on Windows as well, or just on the Mac?

Greg Reader

https://community.logos.com/discussion/comment/101523#Comment_101523

THanks! Will do

Greg Reader

https://community.logos.com/discussion/comment/101679#Comment_101679

Here's the screen shot of Gesenius when open:

Greg Reader

https://community.logos.com/discussion/comment/101523#Comment_101523

Gesenius seems to be working now in A15. Thanks!

Tom Philpot (Faithlife)

https://community.logos.com/discussion/comment/102098#Comment_102098

Gesenius seems to be working now in A15. Thanks!

I don't think we changed anything to get the resource unstuck. Did you do something in the app to get it to work again? I ask because another user has this problem in this thread: http://community.logos.com/forums/p/13172/102337.aspx#102337

Greg Reader

https://community.logos.com/discussion/comment/102339#Comment_102339

No, I didn't change anything. What I did notice was that at first in A15 the problem still seemed to be there, just a little different. When I would try to navigate somewhere in the resource, instead of the program crashing, it just didn't seem to do anything. Then, after I don't know how long, it suddenly started working, and now I can navigate no problem. Almost as if it was waiting for the resource to fully load or something.

Greg