"Logos Stopped Working"
It already didn't seem to want to work (the 30 second delay trick etc)
I was cleaning up a Collection's dynamic syntax - at the same time I had a number ofPhilippians commentaries open that would have been (influenced?) because they were in that same collection.
Regards, SteveF
Comments
-
We'll review your log. Thanks.
The log references Parallel Resource Sets, so I assume your Collection had "Show in parallel resources" selected--is that correct?
I haven't been able to reproduce the crash with one of my collections. In case it helps developers troubleshoot the crash, what was the original Rule syntax in your collection and what were you changing it to?
0 -
Melissa Snyder said:
I assume your Collection had "Show in parallel resources" selected--is that correct
Thanks Melissa
Yes it was checked.
The syntax rule was a long list of typed in (actual) commentary names enclosed in quote marks and separated by commas.
The list has already changed.
I assume it could not cope with having some of those commentaries open.
Or
it may not have liked the fact that I had added/deleted from the syntax the names of commentaries that were open at the time?
Regards, SteveF
0 -
SteveF said:Melissa Snyder said:
I assume your Collection had "Show in parallel resources" selected--is that correct
Thanks Melissa
Yes it was checked.
The syntax rule was a long list of typed in (actual) commentary names enclosed in quote marks and separated by commas.
The list has already changed.
I assume it could not cope with having some of those commentaries open.
Or
it may not have liked the fact that I had added/deleted from the syntax the names of commentaries that were open at the time?
Thank you for the additional information. I submitted your log to development.
Update: A fix for this will be in Beta 5. If the crash reoccurs after installing the beta update (due out this week), please provide new logs. Thanks.
0
