Opening a new window in 5.2 RC and the betas bevor causes a crash and ends logos on my PC (Win8).
Therefor it is unpossible to open Bible reference windows or info-window or the library in an extra window.
How are you trying to open a new window? What window is it that you are opening? I need to know if I am to try to recreate the problem. Thanks.
For example open Bible facts from the menu.
The error occurs always, when logos opens an independent new floating window.
It seems that every new floating windows causes an error. In Logos 5.1 opening of windows was ok.
Hi Thomas
For example open Bible facts from the menu. The error occurs always, when logos opens an independent new floating window.
I've just tried this - running RC1 on Windows 8.1 - and it works fine for me.
Please enable diagnostic logging and post logs after a crash as per https://www.logos.com/support/logos5/windows/problem
Graham
2055.LogosCrash.txt2475.LogosError.logHere are the logs . . .
The Problem exist even in the nonbeta 5.2 version
Thanks for your support. I am looking forward for a solution.
1715.LogosError.log
Thomas
Sorry to hear you are still having a problem.
Is there also a logos.log file available? If so, please upload to this thread.
Here are the crash files once again.
I hope the problem can be fixed quickly, because it is difficult to work with logos not opening any window within.
Sincerly
0310.Logos.log
0525.LogosCrash.txt
4382.LogosError.log
This is an error reported by Windows that's crashing WPF. Unfortunately, due to the nature of the crash, there may not be much we can do about it.
We've had customers report this error when running third-party software that enhances the Windows desktop, such as "Actual Multiple Monitors" (e.g., this forum post: http://community.logos.com/forums/p/64263/452605.aspx#452605).
If you have any multiple desktop, window management, WindowBlinds, theming software, multiple monitor extensions, or anything like that installed, please try disabling it and see if the problem still occurs. There may be a conflict between that software and WPF.
Thanks for your quick investigations! [:)]
With your help I found the problematic programm.
It is "Actual File Folders 1.01"
Thanks for letting us know; we'll add this our knowledgebase in case someone else has the same problem.
