4.2a Beta 5 Crash after clicking on notes
I have several reading plans I use every day. Inside of the reading plans themselves I have the highlighting tool, the resource I am reading, a note file, a dictionary, and the power lookup tool. I use the layout feature as well. I will load a layout to do one of my plans. Each reading plan has its own layout. I simply load the layout, read the resource, take appropriate notes, then update the layout and come back the next time in the same process. It's simple and efficient. The problem is today I am reading Christian Theology Erikson and I load the layout. I can read the resource, but when I click on my notes to take notes it crashes. Here is the log.
Comments
-
The error detail states [quote]Error ID: 8576
Error detail: ArgumentException: Width must be non-negative.
It's only a guess but I think something has gone wrong with your layout. Try recreating the layout from scratch (without preloading that layout) and save it with a temp name.
Close all resources and then reload that new temp layout and see if the problem persists.
Sarcasm is my love language. Obviously I love you. 0 -
Thank you Thomas. I have already made a new layout and it seems to be working fine now.
0 -
Great to hear that you were able to clear up the problem, but I bet a bug still remains in Logos -- any idea how you got it into that situation where it was able to crash? If it could be reproduced that would help Logos track down the problem and fix it.
0 -
Rosie Perera said:
Great to hear that you were able to clear up the problem, but I bet a bug still remains in Logos -- any idea how you got it into that situation where it was able to crash? If it could be reproduced that would help Logos track down the problem and fix it.
Rosie, I have been using Logos for a few years and using the Beta for about a year. I have never had any problems until today. I see the forums daily and have experienced none of those issues ever. I am not really sure what happened. I do not know if I could reproduce the conditions because nothing has changed except I created a new layout. Everything is the same as it has been for the last month. So, I do not know what happened or if it can be reproduced. My reading is done for today, but I will see what happens tomorrow.
Matt
0 -
Here is an update. Today is Monday and Logos still crashes. Talking about the same reading plan.. Christian Theology and today I did not use a layout. I opened the resource, the highlight tool, then my notes. I clicked on the bottom of my notes and it crashed. I reloaded and then loaded my Christian theology notes by itself and clicked on it, when I get to the bottom of the file to input new data it crashes. This is a NOTE bug, not a layout bug.
0 -
Matthew,
The crash log doesn't contain Logos code; however, the error in it has been reported once before (http://community.logos.com/forums/t/23042.aspx). Microsoft has fixed it in .NET 4, so once we are able to upgrade to .NET 4 (when is unknown at this time), this error should be resolved.
0 -
Melissa Snyder said:
Matthew,
The crash log doesn't contain Logos code; however, the error in it has been reported once before (http://community.logos.com/forums/t/23042.aspx). Microsoft has fixed it in .NET 4, so once we are able to upgrade to .NET 4 (when is unknown at this time), this error should be resolved.
Thank you Melissa. [:)]
0 -
Melissa Snyder said:
so once we are able to upgrade to .NET 4 (when is unknown at this time)
Is there any hope of upgrading to .NET4 in the 4.3 beta series? We still are unable to properly display Syriac text (among other things) until Logos is upgraded to .NET4.
0 -
James W Bennett said:Melissa Snyder said:
so once we are able to upgrade to .NET 4 (when is unknown at this time)
Is there any hope of upgrading to .NET4 in the 4.3 beta series? We still are unable to properly display Syriac text (among other things) until Logos is upgraded to .NET4.
FYI... .net4 was released just under a year ago. From other posts, there are other problems that is preventing L4 from using .net4.
0 -
James W Bennett said:Melissa Snyder said:
so once we are able to upgrade to .NET 4 (when is unknown at this time)
Is there any hope of upgrading to .NET4 in the 4.3 beta series? We still are unable to properly display Syriac text (among other things) until Logos is upgraded to .NET4.
An upgrade to .NET 4 is not planned for 4.3, but is on our timeline for a future release.
0 -
Bradley Grainger said:
An upgrade to .NET 4 is not planned for 4.3, but is on our timeline for a future release.
Bradley, is there anyway that we could get an option to turn off the display/rendering of vowel points and/or diacriticals for Syriac (actually would be good for Hebrew and Aramaic also)? For one, this would be a good thing since the ancient texts did not typically use them. It would also allow the Syriac to display properly wouldn't it?
0 -
Bradley Grainger said:
An upgrade to .NET 4 is not planned for 4.3, but is on our timeline for a future release.
Bump.
Ok, it has been two years since this problem was first reported (Nov 2009). We have had two Syriac resource sets released in the last month and the Leiden Peshitta is slated to be released at the end of this month. We are now into the 4.5 Beta series. Can we please have this bug fixed? I may be wrong, but I really expect the number of people with Syriac resources to increase with the release of the Leiden Peshitta since it is THE critical edition. And as this bug effects the display of the text it will not reflect well on the normally high quality of Logos software.
Thanks.
[EDIT]
Sorry, same bug (Logos not using .NET 4) but unrelated symptoms. In the future I'll try and post my requests for this bug fix in the threads appropriate to the symptom I am talking about
Also I must correct myself, the other two Syriac resource sets, like the Leiden Peshitta, are being release later this month.[/EDIT]
0
