Notice: This forum has been recovered from an old backup, so some content, links, and dates may be outdated. The forum is currently read-only while we restore sign-in and registration functionality. Details

If you find this forum valuable and would like to help keep it online, donations to help cover hosting and domain costs are greatly appreciated, but never expected. You can support the forum through Buy Me a Coffee or Ko-fi. Thank you for helping preserve the EventGhost community.

New OSD problem.

If you have a question or need help, this is the place to be.
Post Reply
stisev
Experienced User
Posts: 162
Joined: Tue Jun 26, 2007 2:55 am

New OSD problem.

Post by stisev »

Code: Select all

7:18:11 PM   Error in Action: "Show OSD: OFF (1100MP)  ON (Laptop)"
7:18:11 PM   Traceback (most recent call last) (1483):
7:18:11 PM     File "D:\Applications\EventGhost\eg\Classes\ActionClass.py", line 157, in CallWrapper
7:18:11 PM     File "D:\Applications\EventGhost\plugins\EventGhost\ShowOSD.py", line 410, in __call__
7:18:11 PM     File "wx\_core.pyc", line 14526, in __getattr__
7:18:11 PM   PyDeadObjectError: The C++ part of the OSDFrame object has been deleted, attribute access no longer allowed.
Here is a copy of my XML: http://gothamglow.com/sv/plut.xml

I am receiving this error. I was modifying my config (by adding a few things), but NOTHING was deleted. I'm at a complete loss.

Version 1483 (latest as of 10/28).
User avatar
Bitmonster
Site Admin
Posts: 2239
Joined: Mon Feb 06, 2006 10:28 pm

Re: New OSD problem.

Post by Bitmonster »

The code for the OSD hasn't changed since May. So there must have changed something else on your system. I can't reproduce this error here. Take a look if it has anything to do with another program that is installed.
Please post software-related questions in the forum - PMs will only be answered, if really private, thanks!
stisev
Experienced User
Posts: 162
Joined: Tue Jun 26, 2007 2:55 am

Re: New OSD problem.

Post by stisev »

Bitmonster wrote:The code for the OSD hasn't changed since May. So there must have changed something else on your system. I can't reproduce this error here. Take a look if it has anything to do with another program that is installed.
How utterly bizarre. I just installed build 1484 and the problem was solved.

I'm sorry to have wasted to your time, Bit. I'll let you know and investigate further if the behavior returns.
sev
Post Reply