Re: [Tkinter-discuss] Debugging non-zero exit code

2016-02-07 Thread Michael Lange
Hi, > As I said it disables it correctly, but uses mainloop() to handle > the input. Without it it doesn't input the text in the paper > after pressing Enter. it should certainly be possible to write a handler that does this without a second mainloop. Not sure what causes the problem, maybe it is

Re: [Tkinter-discuss] Debugging non-zero exit code

2016-02-06 Thread Reinis Danne
On Sat, Feb 06, 2016 at 11:10:04PM +0100, Michael Lange wrote: > Hi, > > On Sat, 6 Feb 2016 22:22:38 +0200 > Reinis Danne wrote: > > > No, it is not using threads. The issue seems to be caused by the > > presence of another mainloop() (see > > edit_pool.py::editPool.activate()). I now noticed th

Re: [Tkinter-discuss] Debugging non-zero exit code

2016-02-06 Thread Michael Lange
Hi, On Sat, 6 Feb 2016 22:22:38 +0200 Reinis Danne wrote: > No, it is not using threads. The issue seems to be caused by the > presence of another mainloop() (see > edit_pool.py::editPool.activate()). I now noticed that editPool > calls editPool.mainloop() during activation and then > editPool.q

Re: [Tkinter-discuss] Debugging non-zero exit code

2016-02-06 Thread Reinis Danne
On Sat, Feb 06, 2016 at 08:02:43PM +0100, Michael Lange wrote: > Hi, > > On Sat, 6 Feb 2016 18:43:07 +0200 > Reinis Danne wrote: > > (...) > > Adding root.wm_protocol('WM_DELETE_WINDOW', root.quit) worked > > indeed, but only for the close button. It didn't work if I closed > > the window with A

Re: [Tkinter-discuss] Debugging non-zero exit code

2016-02-06 Thread Michael Lange
Hi, On Sat, 6 Feb 2016 18:43:07 +0200 Reinis Danne wrote: (...) > Adding root.wm_protocol('WM_DELETE_WINDOW', root.quit) worked > indeed, but only for the close button. It didn't work if I closed > the window with Alt+F4 or File->Exit. On further inspection it > already used WM_DELETE_WINDOW pro

Re: [Tkinter-discuss] Debugging non-zero exit code

2016-02-06 Thread Reinis Danne
On Fri, Feb 05, 2016 at 09:09:39PM +0100, Michael Lange wrote: > Hi, > > On Fri, 5 Feb 2016 21:44:04 +0200 > Reinis Danne wrote: > > > Hi! > > > > I'm trying to debug why BKChem prints '0' and exits with exit > > code 1. As far as I can tell that is not directly in the app. > > I tried to debug

Re: [Tkinter-discuss] Debugging non-zero exit code

2016-02-05 Thread Michael Lange
Hi, On Fri, 5 Feb 2016 21:44:04 +0200 Reinis Danne wrote: > Hi! > > I'm trying to debug why BKChem prints '0' and exits with exit > code 1. As far as I can tell that is not directly in the app. > I tried to debug it with gdb, but it tried (and failed) to start > the app again after I have press

[Tkinter-discuss] Debugging non-zero exit code

2016-02-05 Thread Reinis Danne
Hi! I'm trying to debug why BKChem prints '0' and exits with exit code 1. As far as I can tell that is not directly in the app. I tried to debug it with gdb, but it tried (and failed) to start the app again after I have pressed the close button, so I didn't get any useful info out of it. How could