[wingide-users] application and document destroy signals failing to call handlers

Wingware Support support at wingware.com
Thu Sep 18 13:09:01 MDT 2008


Brec Carson wrote:
> I have callbacks setup for the application and document 'destroy' 
> signals.  These never get called.  I can open and close file after file 
> and not get the document close signal and of course exit the application 
> and never see the application 'destroy' handler write out its log 
> statement.  NOTE: I'm logging to an external log file in order to see 
> the application destroy event.
> 
> I have almost every other signal for each component of Wing wired up and 
> all of those seem to working as expected.  This is what makes me 
> suspicious of the Wing in this case and not that I mis-implemented this 
> functionality (though it's definitely possible I admit).
> 
> Any suggestions?

What is the call signature of your signal handler?  I wonder if it's not
matching -- it should take one argument, which is the document object.
I tried it here and it seems to work, so that's my first guess at what
is going wrong in your script.

-- 

Stephan Deibel
Wingware | Python IDE
Advancing Software Development

www.wingware.com



More information about the wingide-users mailing list