A8-Buggy Behavior during 'Open resource'

While trying to reproduce the crash experienced in my last post, the following actions were taken with the accompanying results:

1. Opened the respective layout in which the last crash was produced
2. Clicked on Wiersbe's Expository Outlines in the New Testament (this had been the last action prior to yesterday's crash)
3. L4 began opening the resource in the commentary pane, at which time the commentary pane turned 'gray' and unresponsive, while the PG switched to the Exegetical guide. (see screen shot here 3823.Screen Shot for L4 Bug.tiff)

4. L4 remained in a workable state but buggy and without any visible commentary. Clicking on any resource in the PG resulted in taking me to the Exegetical Guide.
5. After clicking on a few different resources from the PG, and experiencing all of the above mentioned, the commentary window became responsive again and the text reappeared. No more 'grayed out' blank pane. L4 logs are below.

4380.Archive.zip" target="_blank">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/75/4380.Archive.zip:550:0]

Find more posts tagged with

Comments

Jack Caviness

3. L4 began opening the resource in the commentary pane, at which time the commentary pane turned 'gray' and unresponsive, while the PG switched to the Exegetical guide. (see screen shot here

Mark

I don't have the solution, but I thought I would post your screen shot in this thread, so those who can help will not need to download and open it. (The forum will not accept tiff files, but converting it to jpg will work.)

Mark Nigro

https://community.logos.com/discussion/comment/65068#Comment_65068

Thank you, Jack.

I appreciate you uploading the screen shot. I couldn't get it to go up as anything other than a downloadable link. Now I see why. I'll use JPG from now on.

Also note that in this screen shot I had already clicked back to the PG out from the EG. Hopefully the logs will be of help to the developers. The last log I posted had too little information in it because the crash was so quick there simply wasn't much captured.

Jack Caviness

https://community.logos.com/discussion/comment/65093#Comment_65093

I appreciate you uploading the screen shot. I couldn't get it to go up as anything other than a downloadable link. Now I see why. I'll use JPG from now on

I use Grab for screen shots, and it saves them as tiff files. When I could not get them to upload on the forum, I opened in Graphic Converter and saved as jpg, which is rather universal. That did the trick. Now we both know—just don't tell Donavon and Joe, let them figure it out for themselves. [8-|]

Mark Nigro

https://community.logos.com/discussion/comment/65352#Comment_65352

FYI: You can also open the TIFF in 'Preview' and then 'save as' a variety of file types, including JPG. A quick short-cut to Preview is to hit 'Print' right from within 'Grab' when you have taken the screen shot, and then select 'Preview' from the 'Print' window. That saves you the trouble of saving and naming the file, then locating it and opening it in another program, then exporting it again. Just a thought....

Jack Caviness

https://community.logos.com/discussion/comment/65756#Comment_65756

FYI: You can also open the TIFF in 'Preview' and then 'save as' a variety of file types, including JPG. A quick short-cut to Preview is to hit 'Print' right from within 'Grab' when you have taken the screen shot, and then select 'Preview' from the 'Print' window. That saves you the trouble of saving and naming the file, then locating it and opening it in another program, then exporting it again. Just a thought....

Good to know, Thank You.

Jack Caviness

While trying to reproduce the crash experienced in my last post

Mark

Back to the original purpose of this thread. A-9 is due out today. If it does not fix your problem, start another thread with A-9 BUGG in the title.