Now Bible Analyzer won't run at all -- YAY, it works now!

[2mc]

I've reported some issues recently about not being able to download files I purchased and also duplicate tabs. Now, when I start Bible Analyzer, I get the splash screen, but then immediately after the splash screen disappears, I get the following error message. I have reported it through the dialog box of the error message. Here is what it says:

ystem Architecture: 32bit AMD64
Frozen: windows_exe

#---- End System Information ----#


#---- Traceback Info ----#

*** Mon Oct 28 10:05:54 2024 ***
Traceback (most recent call last):
File "analyzer5.py", line 8734, in OnInit
File "analyzer5.py", line 8738, in ShowMain
File "analyzer5.py", line 765, in __init__
File "aui\framemanager.pyc", line 6167, in Update
File "aui\framemanager.pyc", line 6343, in DoUpdate
wx._core.wxAssertionError: C++ assertion "CheckExpectedParentIs(w, m_containingWindow)" failed at ..\..\src\common\sizer.cpp(887) in wxSizer::SetContainingWindow(): Windows managed by the sizer associated with the given window must have this window as parent, otherwise they will not be repositioned correctly.

Please use the window wxFrame@043931C0 ("Bible Analyzer 5.6", HWND=00131938) with which this sizer is associated, as the parent when creating the window wxPanel@06AC6610 ("panel", HWND=0017196C) managed by it.

#---- End Traceback Info ----#

[epement]

Sorry that this issue has gotten worse for you. If the problem is urgent, try this:

Locate the file "%APPDATA%\Bible Analyzer\config.ini" and move it to a location that is unknown to Bible Analyzer, like c:\misc\config.ini (directory name "misc" was picked at random). You can have any directory name you want, as long as BA does not know about it.

The word "move" means to copy the file from the source directory to a different target directory, which may be an existing directory or a new directory created just now. Then delete the file from the source directory.

The Windows variable %APPDATA% should expand to something like "C:\Users\yourname\AppData\Roaming"

When BIble Analyzer loads and finds that "config.ini" is missing from the ~\AppData\Roaming\Bible Analyzer\ directory, it will recreate the file and it will locate all your installed Dictionaries, Commentaries, Reading Plans, and additional things you have added. I am not making this up, because I just tested this on my own Windows 10 Pro system (version 10.0.19045 Build 19045), and Bible Analyzer created a new config.ini file for me.

At your leisure, you can use a file-compare utility like WinMerge or Meld to compare the "bad" and the new config.ini files.

[2mc]

Thanks. I did what you suggested. I compared the files side by side and I made a couple of minor changes in the original config.ini and then put it back in the original location, after eliminating the one that was auto-created.

That got the program to run again with all of my settings and customizations as they were.

Thanks!