Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bpbible portable, Debug -> Display timing or Output Raw error #226

Open
GoogleCodeExporter opened this issue Nov 28, 2015 · 5 comments
Open

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Start bpbible
2. Debug -> enable Display timing or Output Raw

What is the expected output? What do you see instead?

Traceback (most recent call last):
  File "display_options.pyo", line 56, in on_option_clicked
  File "display_options.pyo", line 135, in display_option_changed
  File "util\observerlist.pyo", line 18, in __call__
  File "util\observerlist.pyo", line 22, in _call_function
  File "displayframe.pyo", line 694, in change_display_option
  File "wx\_core.pyo", line 14619, in __getattr__
PyDeadObjectError: The C++ part of the BibleFrame object has been deleted, 
attribute access no longer allowed.

What version of the product are you using? On what operating system?  Is it
the PortableApps version or the standard version?

-> 0.5.1.1

If the problem happens with one particular module (Bible, commentary,
dictionary, or book), what module is it?


Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 21 Mar 2012 at 8:11

@GoogleCodeExporter
Copy link
Author

Hi Markus,

Two questions:
1. Is the Debug menu enabled by default in the PortableApps distribution?  It's 
intended only to be for development, though I sometimes use it for debugging a 
released version.

2. Does this happen after a restart, or does it seem to be a once off thing?

Original comment by [email protected] on 22 Mar 2012 at 1:47

@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 22 Mar 2012 at 1:52

@GoogleCodeExporter
Copy link
Author

Hi Jon,

1. The Debug menu is enabled by default.
2. It does vary and is reproducible.

Original comment by [email protected] on 22 Mar 2012 at 4:17

@GoogleCodeExporter
Copy link
Author

Hi Markus,

When I run a newly installed version of BPBible Portable 0.5.1.1, I do not get 
the Debug menu.  When I enable it with the command line, the menu options you 
mention seem to work for me.  I'm not sure why yours behaves differently.  In 
particular, your traceback looks like the app should be just shutting down, 
which I don't gather it is.

Original comment by [email protected] on 25 Mar 2012 at 1:38

@GoogleCodeExporter
Copy link
Author

Hi Jon,

I use virtualbox with Win 7 guest. The usb connection to the host is very slow. 
See my video in the attachment.


Original comment by [email protected] on 26 Mar 2012 at 4:53

Attachments:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant