I assume you meant to change it in place, and not recompile, right?   
It still stopped at the "creating MainWin", and it still took forever  
for the traceback to actually return something, but here's what it  
gave me:

Traceback (most recent call last):
   File "/opt/local/bin/solfege", line 74, in <module>
     src.mainwin.start_app(os.path.join(prefix, "share", "solfege"))
   File "/opt/local/share/solfege/src/mainwin.py", line 887, in  
start_app
     w.show()
KeyboardInterrupt

And this time, it actually stopped the Python process and spit me back  
to the command prompt.

--Allen



On Sep 30, 2009, at 5:11 PM, Tom Cato Amundsen wrote:

> Comment out line 159 in src/htmlwidget.py. The line looks like this:
>        self.connect("realize", rr)
>
> Change it to:
> #        self.connect("realize", rr)
>
> Does this make any difference?
>
> Tom Cato
>
> On Wed, Sep 30, 2009 at 11:02 PM, Allen McBride <[email protected] 
> > wrote:
>> On Sep 30, 2009, at 4:00 PM, Tom Cato Amundsen wrote:
>>>
>>> I don't know how Mac people gently ask a program to exit ;-)
>>> but on linux, if I start solfege from a terminal window and press
>>> Ctrl-C to stop the program I get a traceback. An example shown  
>>> below.
>>> Can you do that and send me the output? There I can see what the
>>> program is doing.
>>>
>>> Tom Cato
>>
>> Interesting.  I hit Ctrl-C, and thought nothing was happening.  But  
>> after a
>> minute, "Traceback (most recent call last):" appeared, and then  
>> nothing
>> after that for a long time.  Python kept churning, and I did not  
>> get a
>> command prompt again at the terminal.  But then finally, after  
>> maybe 20
>> minutes or so, the terminal showed:
>>
>> Traceback (most recent call last):
>>  File "/opt/local/share/solfege/src/htmlwidget.py", line 143, in rr
>>    def rr(widget):
>> KeyboardInterrupt
>>
>> But the program kept going.  I got a window asking if I wanted to  
>> make an
>> automatic bug report.  I clicked the yes button, but then things  
>> seemed to
>> hang in that window.  Behind that window, I finally got the actual  
>> Solfege
>> main window.  But I can't click any menus on it or anything else.   
>> As I
>> write this, Python is still chugging away.  I'm sending one other  
>> thing:
>> it's the results of "sample process" on the Python process, while  
>> it was
>> hung on the "creating MainWin" stage.  Each sample I take in this  
>> state
>> looks very similar.
>>
>> Thanks!
>> --Allen
>>
>>
>
>
>
> -- 
> Tom Cato Amundsen <[email protected]>                 http:// 
> www.solfege.org/
> GNU Solfege - free ear training    http://www.gnu.org/software/ 
> solfege/


------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
Solfege-devel mailing list
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe", or visit
https://lists.sourceforge.net/lists/listinfo/solfege-devel

Reply via email to